|| ||Pavel Emelyanov <firstname.lastname@example.org> |
|| ||Christoph Lameter <email@example.com>,
Pekka Enberg <firstname.lastname@example.org>, Matt Mackall <email@example.com>,
|| ||[PATCH 0/5] Slab objects identifiers |
|| ||Thu, 06 Oct 2011 20:22:17 +0400|
|| ||Glauber Costa <firstname.lastname@example.org>,
Cyrill Gorcunov <email@example.com>,
Andrew Morton <firstname.lastname@example.org>|
|| ||Article, Thread
While doing the checkpoint-restore in the userspace we need to determine
whether various kernel objects (like mm_struct-s of file_struct-s) are shared
between tasks and restore this state.
The 2nd step can for now be solved by using respective CLONE_XXX flags and
the unshare syscall, while there's currently no ways for solving the 1st one.
One of the ways for checking whether two tasks share e.g. an mm_struct is to
provide some mm_struct ID of a task to its proc file. The best from the
performance point of view ID is the object address in the kernel, but showing
them to the userspace is not good for performance reasons. Thus the ID should
not be calculated based on the object address.
The proposal is to have the ID for slab objects as the mixture of two things -
the number of an object on the slub and the ID of a slab, which is calculated
simply by getting a monotonic 64 bit number at the slab allocation time which
gives us 200+ years of stable work (see comment in the patch #2) :)
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to email@example.com. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"firstname.lastname@example.org"> email@example.com </a>