From owner-freebsd-current Wed Jul 4 9:48:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with SMTP id AC9A837B409 for ; Wed, 4 Jul 2001 09:48:08 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 25785 invoked from network); 4 Jul 2001 16:48:08 -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 ; 4 Jul 2001 16:48:08 -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: Date: Wed, 04 Jul 2001 09:48:05 -0700 (PDT) From: John Baldwin To: Julian Elischer Subject: RE: RFC: Kernel thread system nomenclature. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Jul-01 Julian Elischer wrote: > > The time has come (now that we have a design) to assign names to the > various entities that will be created when we implement the > (current name) KSE code. I'm not sure the current names are all that bad. Hopefully one is going to be doing some reading before diving and modifying this stuff. Here are some suggestions anyways. > Suggested names: proc, task (others?) This should stay 'proc' as it is still the actual process (it holds the pid, etc.) Every reference I've seen to kernels with threads still calls this a process. > Suggested names: schedblock (SB), > Kernel Schedulabale Entity Group (KSEG), > KSE (confusing but acurate), > SchedEntry, (SE?), > Process Schduling control block (pscb) threadgroup (threadgrp), we already have process groups for a set of related processes. > Suggested names: Kernel Schedulable Entity(KSE), > thread container(TC), > Scheduler Virtual processor(SVP), > Scheduler Slot(schedslot, ss?) > Thread processor (tp?) virtcpu > Suggested names: Thread Context Block (TCB) > Kernel Schedulabel Entity Context (KSEC) > Thread Context (TCTX) thread This makes the most sense, and allows curproc to become curthread. This should most definitely _not_ be proc. Get it conceptually right rather than minimize diffs. -- John Baldwin -- 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