From owner-freebsd-hackers Wed May 22 20:20:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA04138 for hackers-outgoing; Wed, 22 May 1996 20:20:20 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA04116; Wed, 22 May 1996 20:20:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA06176; Wed, 22 May 1996 20:14:10 -0700 From: Terry Lambert Message-Id: <199605230314.UAA06176@phaeton.artisoft.com> Subject: Re: Congrats on CURRENT 5/1 SNAP... To: wong@rogerswave.ca (Wong) Date: Wed, 22 May 1996 20:14:09 -0700 (MST) Cc: terry@lambert.org, jehamby@lightside.com, jkh@time.cdrom.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: from "Wong" at May 22, 96 09:17:50 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Mon, 20 May 1996, Terry Lambert wrote: > > The Solaris LWP's are a bit harder. They require kernel preemption and > > multithreading. > > are you sure? last time I look at it, was that LWP is just another process > that at will share somebody's code and data segments. use union to make > use of the process table entries in otherwise regular process table. Bzzzt. 1) per thread kernel stacks 2) kernel reentrancy for async calls 3) see John Dysons note on the process page table being shared. > You are right that they are being used for multithreading in c and ada > implementation. Yes; the libLWP (aioread/aiowrite/aiowait/aiocancel) implementation was never "a supported configuration". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.