From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:30:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9751C37B401; Wed, 2 Apr 2003 14:30:30 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CF1643FA3; Wed, 2 Apr 2003 14:30:29 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32MUKf48719; Wed, 2 Apr 2003 17:30:20 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 17:30:20 -0500 (EST) From: Jeff Roberson To: Julian Elischer In-Reply-To: Message-ID: <20030402172900.I64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Juli Mallett cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:30:30 -0000 On Wed, 2 Apr 2003, Julian Elischer wrote: > > > On Wed, 2 Apr 2003, Juli Mallett wrote: > > > * De: Jeff Roberson [ Data: 2003-04-02 ] > > [ Subjecte: Re: libthr and 1:1 threading. ] > > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > > Also, any ETA on the per process signal mask handing bug in > > > > libthr? Might not be safe to convert everything up front, in > > > > a rush of eager enthusiasm... > > > > > > Which bug is that? I'm not aware of it. > > > > I think Terry is referring to the Uncertainty & Doubt as if it were > > a bug over the lack of a process sigmask (moved into the threads), > > as raised by the M:N group. > > I think this IS a problem. We need a per-process mask. > to block signals that no thread is interested in. > Since M:N threads do not have a kernel thread for each userland thread, > there is nowhere to store this info any more. > Then set the mask to be the same on all threads in the process. The mask is set in swapcontext though so it seems reasonable to me that it is atomically updated when you schedule a new user thread on a kse. > I'd be happy to have it be a per-ksegrp mask actually.. > (to help deliver the signal to the right group to lower the interaction > between UTS's in different groups.) >