Re: [PATCH] Uniquely identifying memory usage

Martijn van Oosterhout (s3100411@student.anu.edu.au)
Fri, 30 Jul 1999 01:18:48 +1000

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Riley Williams: "Re: PATCH: /dev/nvram cleanups."
Previous message: yodaiken@chelm.cs.nmt.edu: "Re: low priority soft RT?"
Maybe in reply to: cd_smith@ou.edu: "[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/

Next message: Riley Williams: "Re: PATCH: /dev/nvram cleanups."
Previous message: yodaiken@chelm.cs.nmt.edu: "Re: low priority soft RT?"
Maybe in reply to: cd_smith@ou.edu: "[PATCH] Uniquely identifying memory usage"