From owner-freebsd-arch Fri Jan 4 19: 8:32 2002 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id B2E1D37B405 for ; Fri, 4 Jan 2002 19:08:29 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 45B1A81E0F; Fri, 4 Jan 2002 21:08:29 -0600 (CST) Date: Fri, 4 Jan 2002 21:08:29 -0600 From: Alfred Perlstein To: Julian Elischer Cc: arch@freebsd.org Subject: Re: freeing thread structures. Message-ID: <20020104210829.T82406@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Fri, Jan 04, 2002 at 06:30:43PM -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Julian Elischer [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