From owner-freebsd-arch  Wed Sep 19 16:46:47 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id 867C137B409; Wed, 19 Sep 2001 16:46:44 -0700 (PDT)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
	by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id RAA19180;
	Wed, 19 Sep 2001 17:46:43 -0600 (MDT)
	(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
	by nomad.yogotech.com (8.8.8/8.8.8) id RAA00967;
	Wed, 19 Sep 2001 17:46:42 -0600 (MDT)
	(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15273.11874.366229.387658@nomad.yogotech.com>
Date: Wed, 19 Sep 2001 17:46:42 -0600
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: julian@FreeBSD.ORG, arch@FreeBSD.ORG
Subject: Re: sigsuspend() and KSE
In-Reply-To: <XFMail.010919161625.jhb@FreeBSD.org>
References: <XFMail.010919161625.jhb@FreeBSD.org>
X-Mailer: VM 6.95 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

> /*
>  * Suspend process until signal, providing mask to be set
>  * in the meantime.  Note nonstandard calling convention:
>  * libc stub passes mask, not pointer, to save a copyin.
>  ***** XXXKSE this doesn't make sense under KSE.
>  ***** Do we suspend the thread or all threads in the process?
>  ***** How do we suspend threads running NOW on another processor?
>  */
> 
> Here's my opinion:
> 
> sigsuspend() just suspends the current thread.  When a signal is posted, it
> wakes up all threads blocked on sigsuspend whose mask matches that signal.  I
> can see it still making sense, but perhaps being of limited usefulness in a
> threaded program.

What has limited usefulness?  Being able to suspend all threads, or
waking up all threads?


Nate

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message