Re: [2.6.6-mm4-ff1] I/O context isolation

[Nick Piggin <nickpiggin@yahoo.com.au>]

FabF wrote:
> On Fri, 2004-05-21 at 09:38, Nick Piggin wrote:
> 
>>FabF wrote:
>>
>>>Jens,
>>>
>>>	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
>>>as_io.
>>>
>>
>>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 do want I/O context to be generic not the whole as_io.
> That export should bring:
> 	-All elevators to use io_context
> 	-source tree to be more self-explanatory
> 	-have a stronger elevator interface
> 

Sorry, my mistake. as_io_context is not nicely hidden away at
the moment. I can't remember why, I think it is only needed
for the declaration... I'll look into moving it into as-iosched.c

*But*, io_context is already exported to all elevators and generic
code.

> 
>>>	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.
> 
> But I guess we can merge that stuff to have "a one way, one place" code
> rather than repeat code in all elv.
> 

I quite like things how they sit right now. The io_context thing
is quite generic so that is fine... CFQ's cfq_queue is fairly
specialised and trying to make it generic is not a very good idea,
especially as no other elevators would make use of it.