From owner-cvs-all@FreeBSD.ORG Mon Mar 31 18:38:43 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7562637B404; Mon, 31 Mar 2003 18:38:43 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BEE143F93; Mon, 31 Mar 2003 18:38:42 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h312cvYY016174; Mon, 31 Mar 2003 21:38:57 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 31 Mar 2003 21:38:57 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: <20030331204128.C64602-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: Jeff Roberson cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Nate Lawson Subject: Re: cvs commit: src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 02:38:44 -0000 On Mon, 31 Mar 2003, Jeff Roberson wrote: > > It's great to be getting this. Can you point me to a document indicating > > how this will be used by KSE? Are we going to have "native threads" > > (thr), KSE, and pthreads? > > I have not written a document for umtx. I will probably write a man > page at some point. I'm not sure that KSE can use umtx directly. Their > requirements are different from thr and so this interface is slightly > tied to the thr idea of threads. > > Currently you could use umtx to synchronize two processes if I wasn't > using the PROC_LOCK() in kern_umtx.c. I could do this if there was > enough interest. It sounds sort of neat anyway. > > The only reason this is tied to threads is because the thr_id_t is the > "struct thread *". I dont think kse currently exposes this to userland > although it could. > > I'm sure I'll talk with the other kse folks at more depth about whether > nor not they can use this for the libkse locks. Do you have any thoughts on how you might authorize inter-process synchronization if not implicitly by requiring that synchronization occur between threads in the same process? One of the nice things about the current model is that there are no concerns about authorization... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories