Re: Using block layer's I/O context api (block/blk-ioc.c) without CFQ.

From: Corrado Zoccolo
Date: Fri Aug 20 2010 - 02:51:38 EST


2010/8/19 Pedro EugÃnio Rocha <pedro.eugenio.rocha@xxxxxxxxx>:
> Hi,
Hi,
>
> Is there a way to use the generic block layer I/O context api
> (block/blk-ioc.c), without
> using cfq specific functions and structs? I'm writing an I/O scheduler
> for my master
> thesis, and I'd like to use my own functions for I/O context handling,
> not cfq's. Sorry
> if I'm missing something here.
Sure. I think you can get an idea by grabbing an old enough kernel
that still has anticipatory scheduler (if I recall correctly, 2.6.32
should have it), and look at its functions.
Or you can look at my post:
http://lists.openwall.net/linux-kernel/2009/06/08/387, where I
implemented a proof-of-concept I/O scheduler based on anticipatory
scheduler. Most of the concepts in that scheduler were later ported to
CFQ.
Do you already have a scheduling algorithm in mind? And what will be
your main purpose/target?

Thanks
Corrado
>
> Thanks,
>
> Pedro EugÃnio Rocha
> --
> 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/
>



--
__________________________________________________________________________

dott. Corrado Zoccolo             mailto:czoccolo@xxxxxxxxx
PhD - Department of Computer Science - University of Pisa, Italy
--------------------------------------------------------------------------
The self-confidence of a warrior is not the self-confidence of the average
man. The average man seeks certainty in the eyes of the onlooker and calls
that self-confidence. The warrior seeks impeccability in his own eyes and
calls that humbleness.
              Â Tales of Power - C. Castaneda
--
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/