Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 24 Sep 2002 01:39:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 24 Sep 2002 01:39:52 -0400 Received: from mx2.elte.hu ([157.181.151.9]:6812 "HELO mx2.elte.hu") by vger.kernel.org with SMTP id ; Tue, 24 Sep 2002 01:39:51 -0400 Date: Tue, 24 Sep 2002 07:53:31 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Andy Isaacson Cc: Larry McVoy , Subject: Re: [ANNOUNCE] Native POSIX Thread Library 0.1 In-Reply-To: <20020923190306.D13340@hexapodia.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1031 Lines: 25 On Mon, 23 Sep 2002, Andy Isaacson wrote: > > 90% of the programs that matter behave exactly like Larry has described. > > IO is the main source of blocking. Go and profile a busy webserver or > > mailserver or database server yourself if you dont believe it. > > There are heavily-threaded programs out there that do not behave this > way, and for which a N:M thread model is completely appropriate. [...] of course, that's the other 10%. [or even smaller.] I never claimed M:N cannot be viable for certain specific applications. But a generic threading library should rather concentrate on the common 90% of the applications. (obviously for simulations the absolute fastest implementation would be a pure userspace state-machine, not a threaded application - M:N or 1:1.) Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/