Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946150AbXBBXCF (ORCPT ); Fri, 2 Feb 2007 18:02:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946152AbXBBXCF (ORCPT ); Fri, 2 Feb 2007 18:02:05 -0500 Received: from smtp.osdl.org ([65.172.181.24]:43743 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946150AbXBBXCB (ORCPT ); Fri, 2 Feb 2007 18:02:01 -0500 Date: Fri, 2 Feb 2007 15:01:32 -0800 (PST) From: Linus Torvalds To: Ingo Molnar cc: Alan , 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 In-Reply-To: <20070202224259.GB1212@elte.hu> Message-ID: References: <20070201083611.GC18233@elte.hu> <20070202104900.GA13941@elte.hu> <20070202195932.15b9b4ed@localhost.localdomain> <20070202213019.202e8db5@localhost.localdomain> <20070202224259.GB1212@elte.hu> 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: 865 Lines: 23 On Fri, 2 Feb 2007, Ingo Molnar wrote: > > but if the application /has/ identified fundamental parallelism, we > /must not/ shut that parallelism off by /designing/ this interface to > use the fibril thing which is a limited cooperative, single-CPU entity. Right. We should for example encourage people to use some kind of paralellizing construct. I know! We could even call them "threads", so to give people the idea that they are independent smaller entities in a thicker "rope", and we could call that bigger entity a "task" or "process", since it "processes" data. Or is that just too far out? Linus - 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/