From owner-freebsd-arch Sun Jan 6 1:34:24 2002 Delivered-To: freebsd-arch@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 2D1BD37B416; Sun, 6 Jan 2002 01:34:19 -0800 (PST) Received: from dialup-209.247.139.117.dial1.sanjose1.level3.net ([209.247.139.117] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16N9h0-0004Xt-00; Sun, 06 Jan 2002 01:34:14 -0800 Message-ID: <3C3819C6.C74B8DDD@mindspring.com> Date: Sun, 06 Jan 2002 01:32:54 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson Cc: Alfred Perlstein , arch@freebsd.org Subject: Re: freeing thread structures. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Robert Watson wrote: > I used to think that idea was cool, and now I just think it's evil. The > reason to have per-thread credentials in kernel is to reduce the > requirement for locking and to allow consistent use of credentials while > in kernel. As Julian notes, having per thread credentials means locking in thread_exit(), when it would not otherwise be necessary. [ ... other argument about the evils of threads with different credentials in the same process ... ] I agree: it's evil. So the question becomes: can we get rid of the locking in the thread_exit() function if we didn't have per thread credentials? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message