From owner-freebsd-current Mon Jul 9 11:12:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id EBB8137B401; Mon, 9 Jul 2001 11:12:56 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.114.Dial1.SanJose1.Level3.net [209.244.104.114]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA09835; Mon, 9 Jul 2001 11:12:54 -0700 (PDT) Message-ID: <3B49F446.59D24F58@mindspring.com> Date: Mon, 09 Jul 2001 11:13:26 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Julian Elischer , current@FreeBSD.ORG, Jason Evans , Peter Wemm Subject: Re: RFC: Kernel thread system nomenclature. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 John Baldwin wrote: > One other note. #2 is conceptually a related group of > #4's, so I think it's name should reflect that. (It's > view as a group of #4's is more important than as being > a part of #1.) So, if you go with lwp (yuck) for #4, #2 > should be lwpgrp or some such. I still think lwp's > overloaded nomenclature is a reason to stay away from it. > *shrug* I agree. SunOS 4.1.3 had a "liblwp", which was basically a user space threading library. Solaris/SVR4 pushes this into the kernel because of SMP scaling (if the only tool you have is threads, everything looks like it's "solved" by threads). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message