Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946171AbXBBXwZ (ORCPT ); Fri, 2 Feb 2007 18:52:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946172AbXBBXwY (ORCPT ); Fri, 2 Feb 2007 18:52:24 -0500 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:49397 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1946171AbXBBXwY (ORCPT ); Fri, 2 Feb 2007 18:52:24 -0500 Date: Sat, 3 Feb 2007 00:04:15 +0000 From: Alan To: Linus Torvalds Cc: Ingo Molnar , Zach Brown , linux-kernel@vger.kernel.org, linux-aio@kvack.org, Suparna Bhattacharya , Benjamin LaHaise Subject: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling Message-ID: <20070203000415.053af657@localhost.localdomain> In-Reply-To: References: <20070201083611.GC18233@elte.hu> <20070202104900.GA13941@elte.hu> <20070202195932.15b9b4ed@localhost.localdomain> <20070202213019.202e8db5@localhost.localdomain> <20070202224259.GB1212@elte.hu> X-Mailer: Claws Mail 2.7.1 (GTK+ 2.10.4; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 815 Lines: 17 > When parallelising "real work", I absolutely agree with you: we should use > threads. But you need to look at what it is we parallelize here, and ask > yourself why we're doing what we're doing, and why people aren't *already* > just using a separate thread for it. Because its a pain in the arse and because its very hard to self tune. If you've got async_anything then the thread/fibril/synchronous/whatever decision can be made kernel side based upon expected cost and other tradeoffs, even if its as dumb as per syscall or per syscall/filp type guessing. Alan - 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/