Messages in this thread |  | | | From | cd_smith@ou ... | | Date | Thu, 29 Jul 1999 10:34:36 -0500 (CDT) | | Subject | Re: [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/
|  |