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

[Benjamin LaHaise]

On Wed, Jan 31, 2007 at 11:25:30AM -0800, Zach Brown wrote:
> >without linking it into the system lists.  The reason I don't think  
> >this
> >approach works (and I looked at it a few times) is that many things  
> >end
> >up requiring special handling: things like permissions, signals,  
> >FPU state,
> >segment registers....
> 
> Can you share a specific example of the special handling required?

Take FPU state: memory copies and RAID xor functions use MMX/SSE and 
require that the full task state be saved and restored.

Task priority is another.  POSIX AIO lets you specify request priority, and 
it really is needed for realtime workloads where things like keepalive 
must be processed at a higher priority.  This is especially important on 
embedded systems which don't have a surplus of CPU cycles.

		-ben
-- 
"Time is of no importance, Mr. President, only life is important."
Don't Email: <dont@xxxxxxxxx>.
-
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/