Date: Fri, 06 Jul 2001 15:27:34 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: Julian Elischer <julian@elischer.org> Cc: current@FreeBSD.ORG, Jason Evans <jasone@canonware.com>, Peter Wemm <peter@wemm.org> Subject: Re: RFC: Kernel thread system nomenclature. Message-ID: <XFMail.010706152734.jhb@FreeBSD.org> In-Reply-To: <3B455C0C.C5E8197C@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06-Jul-01 Julian Elischer wrote: > Peter Wemm wrote: >> >> Jason Evans wrote: >> > On Mon, Jul 02, 2001 at 02:16:16PM -0700, Julian Elischer wrote: > [...] >> > I think there is a clear argument for #1 to be "struct proc". I don't >> > much >> > care what #2, #3, and #4 are called. >> > >> > I am of the rather strong opinion that calling #3/#4 "struct proc" is a >> > bad >> > idea in the long run. Yes, it would reduce the diffs, but it would be >> > terribly confusing to those who weren't versed with the development >> > history >> > of KSEs. >> >> Also keep in mind that netbsd use 'struct lwp *' for #3/#4 (SA has these >> combined into one entity). If there is an easy way to not be gratuitously >> different I think it would be worth it. > > Also comments by several others.. > > Ok so here's how it looks to me now: (still not final) > >#1 struct proc (decided) >#2 struct schedgrp ,lpwg (lwp-group), prigrp (priority-group) > subproc (subprocess) >#3 struct upctx (upcall-context), virtcpu, thrdslot (thread slot) >#4 struct lwp (decided) > > usually the 'lwp' will be passed around so diffs to NetBSD will be > minimalised. One thing to note is that as Vahalia (sp?) points out, lwp on SVR4 and Solaris is actually #3 (a virtual CPU) where as lwp on SunOS is a user-thread. Unfortunately, I think by using overloaded terms you are going to confuse people who come into the project from different backgrounds. I would try and stay with non-ambiguous names if possible. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010706152734.jhb>