Re: [PATCH 0 of 4] Generic AIO by scheduling stacks

[bert hubert]

On Fri, Feb 09, 2007 at 02:33:01PM -0800, Linus Torvalds wrote:

>  - IF the system call blocks, we call the architecture-specific 
>    "schedule_async()" function before we even get any scheduler locks, and 
>    it can just do a fork() at that time, and let the *child* return to the 
>    original user space. The process that already started doing the system 
>    call will just continue to do the system call.

Ah - cool. The average time we have to wait is probably far greater than the
fork overhead, microseconds versus milliseconds. 

However, and there probably is a good reason for this, why isn't it possible
to do it the other way around, and have the *child* do the work and the
original return to userspace?

Would confuse me at lot less in any case.

	Bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/