Messages in this thread | | | From | cd_smith@ou ... | Date | Fri, 30 Jul 1999 23:22:06 -0500 (CDT) | Subject | Re: [PATCH] Uniquely identifying memory usage |
| |
On Fri, 30 Jul 1999, Alexander Viro wrote: > Keep in mind that those animals are reused. OTOH adding a generation > number to mm_struct is trivial - the only static one is init_mm (*never* > happens to be tsk->mm under 2.3.11+, only for kernel threads under the > earlier kernels) and the rest is always created by mm_alloc(). So it's a > matter of one static counter.
Until the counter overflows and then you have to make sure you don't re-use a number that's in use, etc. And the same race that you mention below still applies.
> It's a race unless you are dealing with your children.
You're right, it is a race. So I hereby un-request that this patch be included, and I'll write a new one soon that reorganizes stuff to make usage possible without a race.
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/
| |