[lkml]   [2004]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [2.6.6-mm4-ff1] I/O context isolation
On Fri, 2004-05-21 at 09:57, Nick Piggin wrote:
> 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.

Well ff1 does that "concept split".We have
-Elevator interface
-I/O context
-Block management

As none of you seems OK with further changes, I'll stop my effort right
here but keep thinking ff1 is good :)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [from the cache]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site