[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161004185413.GF4205@htj.duckdns.org>
Date: Tue, 4 Oct 2016 14:54:13 -0400
From: Tejun Heo <tj@...nel.org>
To: Paolo Valente <paolo.valente@...more.it>
Cc: Shaohua Li <shli@...com>, Vivek Goyal <vgoyal@...hat.com>,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
Jens Axboe <axboe@...com>, Kernel-team@...com,
jmoyer@...hat.com, Mark Brown <broonie@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH V3 00/11] block-throttle: add .high limit
Hello, Paolo.
On Tue, Oct 04, 2016 at 07:43:48PM +0200, Paolo Valente wrote:
> > I don't think IO bandwidth does not matter. The problem is bandwidth can't
> > measure IO cost. For example, you can't say 8k IO costs 2x IO resource than 4k
> > IO.
>
> For what goal do you need to be able to say this, once you succeeded
> in guaranteeing bandwidth and low latency to each
> process/client/group/node/user?
For resource partitioning mostly. It's not a single user or purpose
use case. The same device gets shared across unrelated workloads and
we need to guarantee differing levels of quality of service to each
regardless of the specifics of workload. We actually need to be able
to control IO resources.
Thanks.
--
tejun
Powered by blists - more mailing lists