From: "Jamie Lokier" <lk@tantalophile.demon.co.uk>
> Manfred Spraul wrote:
> > I'm not sure that this is the right way: It means that every exec()
> > must call dup_mmap(), and usually only to copy a few hundert
> > bytes. But I don't see a sane alternative. I won't propose to
> > create a temporary file in a kernel tmpfs mount ;-)
>
> Every exec creates a whole new mm anyway, after copying data from the
> old mm. The suggestion is to create the new mm before copying the
> data, and to copy the data from the old mm directly to the new one.
>
exec_mmap currenly avoids mm_alloc()/activate_mm()/mm_drop() for single
threaded apps, and that would become impossible.
I'm not sure how expensive these calls are.
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:23 EST