From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Shaohua Li <shli@fb.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kernel-team@fb.com" <Kernel-team@fb.com>,
"axboe@fb.com" <axboe@fb.com>, "tj@kernel.org" <tj@kernel.org>,
"vgoyal@redhat.com" <vgoyal@redhat.com>
Subject: Re: [PATCH V4 00/15] blk-throttle: add .high limit
Date: Mon, 14 Nov 2016 16:41:33 -0800 [thread overview]
Message-ID: <cac5ee16-1400-2fff-3948-fa1dea997702@sandisk.com> (raw)
In-Reply-To: <20161115000529.GA15160@shli-mbp.local>
On 11/14/2016 04:05 PM, Shaohua Li wrote:
> On Mon, Nov 14, 2016 at 02:46:22PM -0800, Bart Van Assche wrote:
>> On 11/14/2016 02:22 PM, Shaohua Li wrote:
>>> The background is we don't have an ioscheduler for blk-mq yet, so we can't
>>> prioritize processes/cgroups. This patch set tries to add basic arbitration
>>> between cgroups with blk-throttle. It adds a new limit io.high for
>>> blk-throttle. It's only for cgroup2.
>>
>> My understanding of this work is that a significant part of it will have to
>> be reverted once blk-mq supports I/O scheduling, e.g. the code for detecting
>> whether the I/O submitter is idle. Shouldn't this kind of infrastructure be
>> added after support has been added in blk-mq for I/O scheduling?
>
> Sure, if we have a CFQ-like io scheduler for blk-mq, this is largly not
> required. But we don't have one yet and nothing is floating around either. The
> conservative throttling is relatively easy to implement and achive similar
> goal. The throttling could be still useful even with ioscheduler as throttling
> is faster if we are talking about CFQ-like scheduler. I don't think this should
> be blocked to wait for I/O scheduling. There was a long discussion in last
> post, and we agreed the throttling and io scheduler aren't mutually exclusive.
> http://marc.info/?l=linux-kernel&m=147552964708965&w=2
Hello Shaohua,
Thank you for pointing me to the discussion thread about v3 of this
patch series. Did I see correctly that one of the conclusions was that
for users this mechanism is hard to configure? Are we providing a good
service to Linux users by providing a mechanism that is hard to configure?
Thanks,
Bart.
next prev parent reply other threads:[~2016-11-15 0:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 22:22 Shaohua Li
2016-11-14 22:22 ` [PATCH V4 01/15] blk-throttle: prepare support multiple limits Shaohua Li
2016-11-14 22:22 ` [PATCH V4 02/15] blk-throttle: add .high interface Shaohua Li
2016-11-22 20:02 ` Tejun Heo
2016-11-22 23:08 ` Shaohua Li
2016-11-23 21:11 ` Tejun Heo
2016-11-14 22:22 ` [PATCH V4 03/15] blk-throttle: configure bps/iops limit for cgroup in high limit Shaohua Li
2016-11-22 20:16 ` Tejun Heo
2016-11-22 23:11 ` Shaohua Li
2016-11-14 22:22 ` [PATCH V4 04/15] blk-throttle: add upgrade logic for LIMIT_HIGH state Shaohua Li
2016-11-14 22:22 ` [PATCH V4 05/15] blk-throttle: add downgrade logic Shaohua Li
2016-11-22 21:21 ` Tejun Heo
2016-11-22 21:42 ` Tejun Heo
2016-11-22 23:38 ` Shaohua Li
2016-11-14 22:22 ` [PATCH V4 06/15] blk-throttle: make sure expire time isn't too big Shaohua Li
2016-11-14 22:22 ` [PATCH V4 07/15] blk-throttle: make throtl_slice tunable Shaohua Li
2016-11-22 21:27 ` Tejun Heo
2016-11-22 23:18 ` Shaohua Li
2016-11-23 21:17 ` Tejun Heo
2016-11-14 22:22 ` [PATCH V4 08/15] blk-throttle: detect completed idle cgroup Shaohua Li
2016-11-14 22:22 ` [PATCH V4 09/15] blk-throttle: make bandwidth change smooth Shaohua Li
2016-11-23 21:23 ` Tejun Heo
2016-11-24 0:59 ` Shaohua Li
2016-11-14 22:22 ` [PATCH V4 10/15] blk-throttle: add a simple idle detection Shaohua Li
2016-11-23 21:46 ` Tejun Heo
2016-11-24 1:15 ` Shaohua Li
2016-11-28 22:21 ` Tejun Heo
2016-11-28 23:10 ` Shaohua Li
2016-11-29 17:08 ` Tejun Heo
2016-11-14 22:22 ` [PATCH V4 11/15] blk-throttle: add interface to configure think time threshold Shaohua Li
2016-11-23 21:32 ` Tejun Heo
2016-11-24 1:06 ` Shaohua Li
2016-11-28 22:08 ` Tejun Heo
2016-11-28 22:14 ` Shaohua Li
2016-11-14 22:22 ` [PATCH V4 12/15] blk-throttle: ignore idle cgroup limit Shaohua Li
2016-11-14 22:22 ` [PATCH V4 13/15] blk-throttle: add a mechanism to estimate IO latency Shaohua Li
2016-11-14 23:40 ` kbuild test robot
2016-11-15 3:57 ` kbuild test robot
2016-11-29 17:24 ` Tejun Heo
2016-11-29 18:30 ` Shaohua Li
2016-11-29 22:36 ` Tejun Heo
2016-11-14 22:22 ` [PATCH V4 14/15] blk-throttle: add interface for per-cgroup target latency Shaohua Li
2016-11-14 22:22 ` [PATCH V4 15/15] blk-throttle: add latency target support Shaohua Li
2016-11-29 17:31 ` Tejun Heo
2016-11-29 18:14 ` Shaohua Li
2016-11-29 22:54 ` Tejun Heo
2016-11-29 23:39 ` Shaohua Li
2016-11-14 22:46 ` [PATCH V4 00/15] blk-throttle: add .high limit Bart Van Assche
2016-11-15 0:05 ` Shaohua Li
2016-11-15 0:41 ` Bart Van Assche [this message]
2016-11-15 0:49 ` Shaohua Li
2016-11-15 1:18 ` Bart Van Assche
2016-11-15 1:28 ` Shaohua Li
2016-11-15 19:53 ` Bart Van Assche
2016-11-15 21:31 ` Shaohua Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cac5ee16-1400-2fff-3948-fa1dea997702@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=Kernel-team@fb.com \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@fb.com \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®