Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
From: Benjamin LaHaise
Date: Thu Feb 22 2007 - 16:33:36 EST
On Thu, Feb 22, 2007 at 01:23:57PM -0800, Zach Brown wrote:
> As one of the poor suckers who has been fixing bugs in fs/aio.c and
> fs/direct-io.c, I really want everyone to read Ingo's paragraph a few
> times. Have it printed on a t-shirt.
direct-io.c is evil. Ridiculously.
> As an experiment, I'm working on backing the sys_io_*() calls with
> syslets. It's looking very promising so far.
Great, I'd love to see the comparisons.
> >So all in one, i used to think that AIO state-machines have a long-
> >place within the kernel, but with syslets i think i've proven myself
> >embarrasingly wrong =B-)
> Welcome to the party :).
Well, there are always the 2.4 patches which are properly state drive and
reasonably simple. Retry was born out of a need to come up with a mechanism
that had less impact on the core kernel code, and yes, it seems to be a
failure and in dire need of replacement.
One other implementation to consider is actually using kernel threads
compared to how syslets perform. Direct IO for one always blocks, so
there shouldn't be much of a performance difference compared to syslets,
with the bonus that no arch specific code is needed.
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@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/