lkml.org 
[lkml]   [1999]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Uniquely identifying memory usage
>The patch has one known issue that really ought to be solved if it
>becomes actually a part of the kernel: It uses the process ID of the first
>process to use a mm_struct as the ID for that struct. This means that
>under the following scenario, the scheme fails:

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.

HTH,

Martijn van Oosterhout
Australia

-
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:0.056 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site