[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed038eb20806180816w5a4f9d6bt276dec1373758e08@mail.gmail.com>
Date: Wed, 18 Jun 2008 17:16:56 +0200
From: "Carl Henrik Lunde" <chlunde@...g.uio.no>
To: "Andrea Righi" <righi.andrea@...il.com>
Cc: balbir@...ux.vnet.ibm.com, menage@...gle.com, matt@...ehost.com,
roberto@...it.it, randy.dunlap@...cle.com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] i/o bandwidth controller documentation
On Sat, Jun 7, 2008 at 00:27, Andrea Righi <righi.andrea@...il.com> wrote:
[...]
> +3. Advantages of providing this feature
> +
> +* Allow QoS for block device I/O among different cgroups
I'm not sure if this can be called QoS, as it does not guarantee
anything but throttling?
> +* The bandwidth limitations are guaranteed both for synchronous and
> + asynchronous operations, even the I/O passing through the page cache or
> + buffers and not only direct I/O (see below for details)
The throttling does not seem to cover the I/O path for XFS?
I was unable to throttle processes reading from an XFS file system.
Also I think the name of the function cgroup_io_account is a bit too innocent?
It sounds like a inline function "{ io += bytes; }", not like
something which may sleep.
--
Carl Henrik
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists