Hi Chandra,
> > Could I ask that you briefly enumerate
> >
> > a) which controllers you think we'll need in the forseeable future
> >
>
> Our main object is to provide resource control for the hardware
> resources: CPU, I/O and memory.
>
> We have already posted the CPU controller.
>
> We have two implementations of memory controller and a I/O controller.
>
> Memory controller is understandably more complex and controversial, and
> that is the reason we haven't posted it this time around (we are looking
> at ways to simplify the design and hence the complexity). Both the
> memory controllers has been posted to linux-mm.
>
> I/O controller is based on CFQ-scheduler.
>
> > b) what they need to do
(snip)
> I/O Controller that we are working on is based on CFQ scheduler and
> provides bandwidth control.
> >
> > c) pointer to prototype code if poss
(snip)
> i/o controller: This controller is not ported to the framework posted,
> but can be taken for a prototype version. New version would be simpler
> though.
I think controlling I/O bandwidth is right way to go.
However, I think you need to change the design of the controller a bit.
A lot of I/O requests processes issue will be handled by other contexts.
There are AIO, journaling, pdflush and vmscan, which some kernel threads
treat instead of the processes.
The current design looks not to care about this.
Thanks,
Hirokazu Takahashi.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
