[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130708175607.GB18600@mtj.dyndns.org>
Date: Mon, 8 Jul 2013 10:56:07 -0700
From: Tejun Heo <tj@...nel.org>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Konstantin Khlebnikov <khlebnikov@...nvz.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...e.cz>,
cgroups@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Sha Zhengju <handai.szj@...il.com>, devel@...nvz.org,
Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH RFC] fsio: filesystem io accounting cgroup
Hello, Vivek.
On Mon, Jul 08, 2013 at 01:52:01PM -0400, Vivek Goyal wrote:
> > Again, a problem to be fixed in the stack rather than patching up from
> > up above. The right thing to do is to propagate pressure through bdi
> > properly and let whatever is backing the bdi generate appropriate
> > amount of pressure, be that disk or network.
>
> Ok, so use network controller for controlling IO rate on NFS? I had
> tried it once and it did not work. I think it had problems related
> to losing the context info as IO propagated through the stack. So
> we will have to fix that too.
But that's a similar problem we have with blkcg anyway - losing the
dirtier information by the time writeback comes down through bdi. It
might not be exactly the same and might need some impedance matching
on the network side but I don't see any fundamental differences.
Thanks.
--
tejun
--
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