From owner-freebsd-current Wed Jul 3 1:54: 4 2002 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 79A1A37B400 for ; Wed, 3 Jul 2002 01:54:00 -0700 (PDT) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2547243E52 for ; Wed, 3 Jul 2002 01:54:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0018.cvx22-bradley.dialup.earthlink.net ([209.179.198.18] helo=mindspring.com) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17PftZ-0000GG-00; Wed, 03 Jul 2002 04:53:54 -0400 Message-ID: <3D22BB53.67E83C85@mindspring.com> Date: Wed, 03 Jul 2002 01:52:35 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Bruce Evans , Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: KSE signal problems still References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Julian Elischer wrote: > Should ALL threads be awakened, or is it enough if ONE thread awakens to > deliver the thread. > > For right now it's mostly important that single threaded processs act > as they used to. We can always change how multithreaded processes > work. POSIX makes no guarantees for threads delivery of signals. Specifically, signals are not thread-things, they are process things, and there are seperate threads-things for sending the moral equivalents (e.g. pthread_kill) to threads on an individual basis, but the system is not expected to make a distinction on signal delivery as to what theread is running, nor are there expected to be per thread masking, etc.. Garrett would probably be the right person to ask; he's a much better POSIX lawyer. This is really the problem I tried to explain earlier when it came to the disabling on SIG_POLL on a per descriptor basis. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message