Date: Mon, 23 Jan 2006 20:00:08 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: julian@elischer.org Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: kernel thread as real threads.. Message-ID: <20060123.200008.84910888.imp@bsdimp.com> In-Reply-To: <43D56E79.60504@elischer.org> References: <43D56468.1060101@elischer.org> <20060123232836.M48094@fledge.watson.org> <43D56E79.60504@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <43D56E79.60504@elischer.org>
Julian Elischer <julian@elischer.org> writes:
: > - fork (although davidxu is changing that)
:
: well, the operation woudll continue for the parent only I woudl assume.
:
: > (although davidxu is changing that)
:
: I'm not convinced that that multiple threads should be allowed to
: proceed during a fork
: but I can see that not allowing it is more a "foot shooting avoidance"
: than a requirement.
: it could be allowed that if you do a fork and allow multipel threads to
: runat the same time
: and end up with an inconsistant address space in the child, then you get
: what you deserve.
: :-)
Why not? It is a race no matter what... And if you do single thread
things, you can run into a bunch of different dead-lock scenarios. I
helped to find one recently with nfs.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060123.200008.84910888.imp>