[CRIU] [PATCH RFC 0/2] Mount point hash
Pavel Emelyanov
xemul at virtuozzo.com
Wed Mar 23 04:14:22 PDT 2016
On 03/17/2016 03:53 PM, Stanislav Kinsburskiy wrote:
> This series introduces hash for mount points.
> The major reason for it is upcomming NFS migration, which is expected to
> heavily search over mount points by mnt_id (to be able to get file system ID
> instead of statfs() call, for instance).
> The idea is trivial and doesn't require an explicit explanation.
> However, there will be two sets of mount points is this series is merged: hash
> and list.
> List looks redundant and less efficient. Traversing hash table for all the
> mounts has the same complexity as over the list: O(n).
> But replacing the list with hash will require a lot or code refactoring, and
> I'm not sure, does it worth it.
The mnt_id, which you plan to use to lookup fstype for file descriptors,
was introduced later than 3.11, thus this patch won't make any use for
this kernel.
> BTW, more hashes can be introduced (with s_dev as a key, for instance; or by
> fs->type).
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
> .
>
More information about the CRIU
mailing list