From owner-freebsd-threads@FreeBSD.ORG Sat Jun 14 03:32:48 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BDA937B401 for ; Sat, 14 Jun 2003 03:32:48 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A37E43FB1 for ; Sat, 14 Jun 2003 03:32:47 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5EAWkhS039154; Sat, 14 Jun 2003 03:32:47 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5EAWkLg007717; Sat, 14 Jun 2003 03:32:46 -0700 (PDT) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h5EAWk6n007716; Sat, 14 Jun 2003 03:32:46 -0700 (PDT) Date: Sat, 14 Jun 2003 03:32:46 -0700 From: Marcel Moolenaar To: David Xu Message-ID: <20030614103246.GA7693@athlon.pn.xcllnt.net> References: <20030614081853.GD5563@athlon.pn.xcllnt.net> <001301c3325f$9c55b390$0701a8c0@tiger> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001301c3325f$9c55b390$0701a8c0@tiger> User-Agent: Mutt/1.5.4i cc: threads@freebsd.org Subject: Re: PTHREADED -> P_SA X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2003 10:32:48 -0000 On Sat, Jun 14, 2003 at 06:27:49PM +0800, David Xu wrote: > > > On Sat, Jun 14, 2003 at 02:56:36PM +0800, David Xu wrote: > > > > > > > I will rename flag P_THREADED to P_SA in kernel, any objections ? > > > > here is the patch: > > > > http://people.freebsd.org/~davidxu/P_SA.diff > > > > > > > > It's only semantics.. > > > > but it's been changes before.. is this the final name? > > > > > > Yes, I think it should be final. > > > > P_THREADED says more than P_SA for someone who's not intimate > > with the code. I for one don't know what SA stands for, but > > apparently it's some kind of threading model/implementation > > if I can believe the comments. In that case I don't know what's > > so wrong about P_THREADED. > > > > So, why is P_SA better than P_THREADED? > > > If you find there is 1:1 threading mode Jeff added in kernel, > I bet you will understand why I need to change it to P_SA. > why shouldn't 1:1 code be called as P_THREADED ? I think this > flags is confusing. P_SA tells you that the threading mode > a process is using is Scheduler Activation based --- Anderson's > theory. Yes, that is a logical explanation. Maybe it helps to have the term Scheduler Activation mentioned somewhere in the context of P_SA. Or, maybe use P_SCHEDACT? I don't object to P_SA, but I know that if I look at the code that references P_SA in a couple of weeks/months, I'm going to wonder what it means all over again. But then again, that may be just me :-) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net