From owner-freebsd-current Tue May 22 4:48:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5450237B43C for ; Tue, 22 May 2001 04:48:50 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4MBmdG58569; Tue, 22 May 2001 04:48:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105220637.f4M6bDD40713@rina.r.dl.itc.u-tokyo.ac.jp> Date: Tue, 22 May 2001 04:48:38 -0700 (PDT) From: John Baldwin To: Seigo Tanimura Subject: RE: New strategy of locking a process group Cc: current@FreeBSD.org 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 22-May-01 Seigo Tanimura wrote: > For now, p_mtx protects p_pgrp in struct proc. This is quite > troublesome for the following reason: Err, it doesn't really. It's mostly undecided at this point. Also, have you looked at the BSD/OS code on builder? They have process groups and sessions already locked not using global locks but using per-data structure locks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message