From owner-freebsd-current Tue Jul 3 15: 8:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 3F0EA37B407 for ; Tue, 3 Jul 2001 15:08:19 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA12761; Wed, 4 Jul 2001 08:07:36 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01K5IY72Z2EOVFB1LE@cim.alcatel.com.au>; Wed, 4 Jul 2001 08:07:14 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f63M7Yf65336; Wed, 04 Jul 2001 08:07:34 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 04 Jul 2001 08:07:33 +1000 From: Peter Jeremy Subject: Re: RFC: Kernel thread system nomenclature. In-reply-to: ; from julian@elischer.org on Mon, Jul 02, 2001 at 02:16:16PM -0700 To: Julian Elischer Cc: current@FreeBSD.ORG Mail-Followup-To: Julian Elischer , current@FreeBSD.ORG Message-id: <20010704080733.C506@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: 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 2001-Jul-02 14:16:16 -0700, 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 reasonably sure that there's prior art here. What do other OS's call these entities? Our naming convention should at least be not inconsistent, and preferably consistent with other implementations. This is especially true for related implementations (BSDi and *BSD - if any of them have gone this path). This affects code portability between the *BSDs, developers who use multiple Unix variants as well as 3rd party vendors. >The exctent of these edits almost makes it worthwhile to call the #4 item >'struct proc' as the size of the diff would be MASSIVLY reduced.. :-). IMHO, what we call #4 has the biggest impact (extending to what we can reasonable call #1). As I see it, the tradeoffs are: Keeping the same name: + Everyone is familiar with it - The entity it references is no longer a `process' and hence the name is no longer descriptive. Changing the name: + The chosen name would be descriptive of its contents. - Massive diffs required (I count ~5200 references in 648 files in /sys and there are more references in userland). Personally, I'd prefer to see struct proc renamed to reflect its new role as a thread context. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message