From owner-freebsd-arch Wed Dec 12 16:47:12 2001 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 0A39637B447 for ; Wed, 12 Dec 2001 16:46:58 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 8348081D01; Wed, 12 Dec 2001 18:46:52 -0600 (CST) Date: Wed, 12 Dec 2001 18:46:52 -0600 From: Alfred Perlstein To: Julian Elischer Cc: Julian Elischer , arch@freebsd.org Subject: Re: Threads, KSEs etc. during exit. Message-ID: <20011212184652.C79896@elvis.mu.org> References: <20011212172324.V92148@elvis.mu.org> 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 Wed, Dec 12, 2001 at 03:49:17PM -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 [011212 18:00] wrote: > > That's one of the possibilities I am considering, but you don't want to > put too much extra testing etc on outgoing path of swtch() as it is called > a hell of a lot. It's also worth wondering if it's enough to store a > single 'to be freed' thread in the pcpu area or whether we need an open > ended scheme. The answer to that would depend on whether we could recurse > before we had the chance to free what we alreay have there. As I've said, it's more important to get it right than to make it fast, we can make it fast later. Why not just implement my solution? it will be pleasantly simple. > The freeing requires some "relatively complicated" things, > e.g. freeing stack pages back to the vm, possibly freeing > the vm-object associated with it, and maybe placing the thread structure > back in the thread-zone for re-allocation. It is a question as to whether > we may ever want to free the memory back to the system after > a process with massive threading exits. Yes, all valid points, but they have no bearing(sp?) without a working implementation. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message