[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191003164552.GA3247445@devbig004.ftw2.facebook.com>
Date: Thu, 3 Oct 2019 09:45:52 -0700
From: Tejun Heo <tj@...nel.org>
To: Michal Koutný <mkoutny@...e.com>
Cc: hannes@...xchg.org, clm@...com, dennisz@...com,
Josef Bacik <jbacik@...com>, kernel-team@...com,
newella@...com, lizefan@...wei.com, axboe@...nel.dk,
Paolo Valente <paolo.valente@...aro.org>,
Rik van Riel <riel@...riel.com>, josef@...icpanda.com,
cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/10] blkcg: implement blk-iocost
Hello,
On Thu, Oct 03, 2019 at 04:51:06PM +0200, Michal Koutný wrote:
> > Initially, I put them under block device sysfs but it was too clumsy
> > with different config file formats and all.
> Do you have any more details on that? In the end, it all boils down to a
> daemon/setup utility writing into the control files and it can use
> whatever config files it decides, can't it?
Yeah, I mean, we can make any interface work. So, there are two
global knobs io.cost.model and io.cost.qos. Of the tw, io.cost.model
is okay to move under block device but the qos file gets weird because
the content of the file is more resource control policies than device
properties.
Thanks.
--
tejun
Powered by blists - more mailing lists