Date: Fri, 4 Jan 2002 21:08:29 -0600 From: Alfred Perlstein <bright@mu.org> To: Julian Elischer <julian@elischer.org> Cc: arch@freebsd.org Subject: Re: freeing thread structures. Message-ID: <20020104210829.T82406@elvis.mu.org> In-Reply-To: <Pine.BSF.4.21.0201041800010.28827-100000@InterJet.elischer.org>; from julian@elischer.org on Fri, Jan 04, 2002 at 06:30:43PM -0800 References: <Pine.BSF.4.21.0201041800010.28827-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Julian Elischer <julian@elischer.org> [020104 20:57] wrote: > > In mi_switch AFTER the switch to the new thread has been completed, > (which is one possibility) the sched lock is held, so freeing any resource > that wants to own a normal sleeping mutex would seem to be an instant > panic. ANother possibility is to simply queue it for later freeing by > another entity, but I REALLY would rather avoid having a reaper thread (or > init) do it. Please just use a reaper thread for now, it will not stop you from optimizing it later. Haven't we gone over this? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020104210829.T82406>