lkml.org 
[lkml]   [1999]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH] Uniquely identifying memory usage
On Fri, 30 Jul 1999, Martijn van Oosterhout wrote:
> Wouldn't it be a lot easier if the id was simply current->mm?
> Thus when CLONE_MM is used they get the same number. Guarenteed
> never to be reused while in use.

Yeah, it would. Is there any good reason not to do this? If this doesn't
have problems, why isn't the same thing done for other kernel ID's? I
can't think of a single place in the kernel where kernel space pointers
get exported to user space as opaque handles, and that makes me nervous
about being the first person to do it. (OTOH, I can think of several
places where NT does this... which makes me even more nervous about doing
it in Linux. <g>)

Chris Smith <cd_smith@ou.edu>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:4.895 / U:0.236 seconds]
©2003-2011 Jasper Spaans. Advertise on this site