Date: Wed, 21 Nov 2001 23:22:09 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: arch@FreeBSD.ORG, Julian Elischer <julian@elischer.org> Subject: Re: Kernel Thread scheduler Message-ID: <XFMail.011121232209.jhb@FreeBSD.org> In-Reply-To: <20011121212416.A88350@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22-Nov-01 Steve Kargl wrote: > 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. Perhaps if 'proc' is put under _KERNEL. Since proc embeds a kse, ksegroup, and thread, it can't very easily be defined w/o including those definitions. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.011121232209.jhb>