From owner-freebsd-arch Wed Nov 21 23:22:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 5C20D37B41A for ; Wed, 21 Nov 2001 23:22:10 -0800 (PST) Received: (qmail 5278 invoked from network); 22 Nov 2001 07:22:14 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Nov 2001 07:22:14 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011121212416.A88350@troutmask.apl.washington.edu> Date: Wed, 21 Nov 2001 23:22:09 -0800 (PST) From: John Baldwin To: Steve Kargl Subject: Re: Kernel Thread scheduler Cc: arch@FreeBSD.ORG, Julian Elischer 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 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 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 <>< 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