From owner-freebsd-current Mon Jun 4 22:59:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 2261F37B405 for ; Mon, 4 Jun 2001 22:59:47 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with ESMTP id f555xiD26685 ; Tue, 5 Jun 2001 14:59:44 +0900 (JST) Message-Id: <200106050559.f555xiD26685@rina.r.dl.itc.u-tokyo.ac.jp> Date: Tue, 05 Jun 2001 14:59:44 +0900 From: Seigo Tanimura To: current@FreeBSD.org Cc: tanimura@r.dl.itc.u-tokyo.ac.jp Subject: Re: Lock of struct filedesc, file, pgrp, session and sigio In-Reply-To: In your message of "Thu, 31 May 2001 16:31:21 +0900" <200105310731.f4V7VLD29187@rina.r.dl.itc.u-tokyo.ac.jp> References: <200105310731.f4V7VLD29187@rina.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII 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 Thu, 31 May 2001 16:31:21 +0900, Seigo Tanimura said: Seigo> Lock of struct filedesc, file, pgrp, session and sigio is now ready Seigo> for testing. Although the patch is still under test, a new task proposal comes to my mind. A new task: lock underlying objects of struct file, namely a vnode, a socket, a pipe, a fifo and an event queue. A socket and a pipe is not mpsafe for now. A vnode (and a fifo) has an interlock, so it might already be mpsafe. An event queue is... up to jlemon? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message