From owner-freebsd-current Sun May 23 17:14: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id BD63014E44 for ; Sun, 23 May 1999 17:13:58 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 5311763; Mon, 24 May 1999 08:13:57 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Bruce Evans , dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages In-reply-to: Your message of "Sun, 23 May 1999 08:57:01 +0200." <7757.927442621@critter.freebsd.dk> Date: Mon, 24 May 1999 08:13:57 +0800 From: Peter Wemm Message-Id: <19990524001357.5311763@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <199905230245.MAA13333@godzilla.zeta.org.au>, Bruce Evans writes: > >>calcru() access p_stats, which is in upages. Therefore, as I understand, > >>it should not be called on a swapped out process. Neither calcru() nor > > > >Does anyone object to moving everything except the stack from the upages > >to the proc table? > > not me. I'd also like to implement a proper clone(2) ala Linux. We have most of the infrastructure in place already, using that and comparing with NetBSD's take on the subject should be fairly useful in the end. The main difference between clone(2) and rfork(2) is that clone() takes a stack argument and is more specific about certain sharing semantics. At present these are emulated via flags added into rfork's visibility, I think it would be cleaner to just use a proper syscall interface onto fork1() rather than bend rfork(2) even more. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message