Re: [2.6.6-mm4-ff1] I/O context isolation
From: Jens Axboe
Date: Fri May 21 2004 - 02:53:47 EST
On Fri, May 21 2004, Nick Piggin wrote:
> FabF wrote:
> > Here's ff1 patchset to have generic I/O context.
> >ff1 : Export io context operations from blkdev/ll_rw_blk (ok)
> >ff2 : Make io_context generic plateform by importing IO stuff from
> Can I just ask why you want as_io_context in generic code?
> It is currently nicely hidden away in as-iosched.c where
> nobody else needs to ever see it.
I think (it's the only reason I can think of) that he is trying to make
the anticipation generic. Am I correct?
> > AFAICS, cfq_queue for instance could disappear when using io_context
> >but I think elv_data should remain elevator side....
> >I don't want to go in the wild here so if you've got suggestions, don't
> >hesitate ;)
> cfq_queue is per-queue-per-process. io_context is just
> per-process, so it isn't a trivial replacement.
Definitely not, I struggled quite a bit with such a transformation in
cfq + ioprio.
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/