Date: Wed, 21 Nov 2001 21:24:16 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Julian Elischer <julian@elischer.org> Cc: arch@FreeBSD.ORG Subject: Re: Kernel Thread scheduler Message-ID: <20011121212416.A88350@troutmask.apl.washington.edu> In-Reply-To: <Pine.BSF.4.21.0111211208410.35591-100000@InterJet.elischer.org>; from julian@elischer.org on Wed, Nov 21, 2001 at 04:39:18PM -0800 References: <Pine.BSF.4.21.0111211208410.35591-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <sys/user.h> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011121212416.A88350>