Date: Tue, 06 Feb 2007 13:31:40 -0800 (PST)
Message-Id: <20070206.133140.91442326.davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: kent.overstreet@gmail.com, davidel@xmailserver.org, zach.brown@oracle.com,
       mingo@elte.hu, linux-kernel@vger.kernel.org, linux-aio@kvack.org,
       suparna@in.ibm.com, bcrl@kvack.org
Subject: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
From: David Miller <davem@davemloft.net>
In-Reply-To: <Pine.LNX.4.64.0702061325380.8424@woody.linux-foundation.org>
References: <Pine.LNX.4.64.0702061238300.8424@woody.linux-foundation.org>
	<20070206.131631.82049180.davem@davemloft.net>
	<Pine.LNX.4.64.0702061325380.8424@woody.linux-foundation.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 673
Lines: 16

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue, 6 Feb 2007 13:28:34 -0800 (PST)

> Yeah, in 1% of all cases it will block, and you'll want to wait for them. 
> Maybe the kevent queue works then, but if it needs any more setup than the 
> nonblocking case, that's a big no.

So the idea is to just run it to completion if it won't block and use
a fibril if it would?

kevent could support something like that too.
-
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/