From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262377AbUKVVnV (ORCPT ); Mon, 22 Nov 2004 16:43:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262379AbUKVVnA (ORCPT ); Mon, 22 Nov 2004 16:43:00 -0500 Received: from cantor.suse.de ([195.135.220.2]:59616 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S262347AbUKVVfL (ORCPT ); Mon, 22 Nov 2004 16:35:11 -0500 Date: Mon, 22 Nov 2004 22:34:48 +0100 From: Andi Kleen To: "Boehm, Hans" Cc: Ray Bryant , Andi Kleen , Andreas Schwab , Kernel Mailing List , linux-ia64@vger.kernel.org, lse-tech , holt@sgi.com, Dean Roe , Brian Sumner , John Hawkes Subject: Re: [Lse-tech] scalability of signal delivery for Posix Threads Message-ID: <20041122213448.GA16153@wotan.suse.de> References: <65953E8166311641A685BDF71D865826058B5C@cacexc12.americas.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65953E8166311641A685BDF71D865826058B5C@cacexc12.americas.cpqcorp.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > I think this is a more general issue. Special casing one It just cannot be done in the general case without slowing down sigaction significantly. Or maybe it can, but nobody has proposed a way to do it so far. It's difficult to design for machines where a simple spinlock doesn't work properly anymore. > piece of it is only going to make performance more surprising, > something I think should be avoided if at all possible. The special case in particular would be signals directed to a specific TID; compared to signals load balanced over the thread group which needs shared writable state. To simplify the fast path you could also make more simplications: no queueing (otherwise you would need to duplicate a lot of state to handle that into the task_struct) and probably no SIGCHILD which is also full of special cases. -And