From owner-freebsd-arch Wed Nov 21 21:24:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 39E2C37B416 for ; Wed, 21 Nov 2001 21:24:18 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id fAM5OGX88404; Wed, 21 Nov 2001 21:24:16 -0800 (PST) (envelope-from sgk) Date: Wed, 21 Nov 2001 21:24:16 -0800 From: Steve Kargl To: Julian Elischer Cc: arch@FreeBSD.ORG Subject: Re: Kernel Thread scheduler Message-ID: <20011121212416.A88350@troutmask.apl.washington.edu> 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 Wed, Nov 21, 2001 at 04:39:18PM -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 On Wed, Nov 21, 2001 at 04:39:18PM -0800, Julian Elischer wrote: > > > recap: > "thread".. structure that is associated with a running context, running in > the kernel.. has a stack, and storage for registers when blocked.. > WHen a system call starts, the 'current' thread is used. WHen it blocks, a > new one is created to return to the userland and collect more work. When > the syscall finishes, the thread may be freed back rto a system wide pool > of threads, unless it is the last one in the KSE, in which case it remains > 'current' and in reserve for the next syscall. > I just spent a week debating namespace pollution with the wine developers [1]. Is there any chance all this work will be protected by #define _KERNEL? [1] Our struct thread in conflicts with the struct thread in wine. Fortunately, we can currently work around this conflict. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message