Re: [PATCH 1/3] i/o bandwidth controller documentation

[Andrea Righi]

Randy Dunlap wrote:
> On Sat,  7 Jun 2008 00:27:28 +0200 Andrea Righi wrote:
>
> > Documentation of the block device I/O bandwidth controller: description, usage,
> > advantages and design.
> >
> > Signed-off-by: Andrea Righi <righi.andrea@xxxxxxxxx>
> > ---
> >  Documentation/controllers/io-throttle.txt |  150 +++++++++++++++++++++++++++++
> >  1 files changed, 150 insertions(+), 0 deletions(-)
> >  create mode 100644 Documentation/controllers/io-throttle.txt
> >
> > diff --git a/Documentation/controllers/io-throttle.txt b/Documentation/controllers/io-throttle.txt
> > new file mode 100644
> > index 0000000..5373fa8
> > --- /dev/null
> > +++ b/Documentation/controllers/io-throttle.txt
> > @@ -0,0 +1,150 @@
> > +
> > +               Block device I/O bandwidth controller
> > +
> > +1. Description
> > +
> > +This controller allows to limit the I/O bandwidth of specific block devices for
> > +specific process containers (cgroups) imposing additional delays on I/O
> > +requests for those processes that exceed the limits defined in the control
> > +group filesystem.
> > +
> > +Bandwidth limiting rules offer better control over QoS with respect to priority
> > +or weight-based solutions that only give information about applications'
> > +relative performance requirements.
> > +
> > +The goal of the I/O bandwidth controller is to improve performance
> > +predictability and QoS of the different control groups sharing the same block
> > +devices.
> > +
> > +NOTE: if you're looking for a way to improve the overall throughput of the
> > +system probably you should use a different solution.
> > +
> > +2. User Interface
> > +
> > +A new I/O bandwidth limitation rule is described using the file
> > +blockio.bandwidth.
> > +
> > +The same file can be used to set multiple rules for different block devices
> > +relatively to the same cgroup.
>
>    relative

I will fix it in the next version.

Thanks again Randy.

-Andrea
--
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/