public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Shaohua Li <shli@kernel.org>
Cc: Khazhismel Kumykov <khazhy@google.com>,
	axobe@kernel.dk, shli@fb.com, tj@kernel.org,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [RFC PATCH] blk-throttle: add burst allowance.
Date: Thu, 7 Dec 2017 14:43:34 -0500	[thread overview]
Message-ID: <20171207194333.GB4067@redhat.com> (raw)
In-Reply-To: <20171116165033.4noofd6gkaj6x3yl@kernel.org>

On Thu, Nov 16, 2017 at 08:50:33AM -0800, Shaohua Li wrote:

[..]
> Can you describe why we need this? It would be great if you can describe the
> usage model and an example. Does this work for io.low/io.max or both?

Hi Shaohua,

Is there any documentation for "io.low" somewhere now. Should we update
cgroup-v2.txt? Just reading through BLK_DEV_THROTTLING_LOW description
does not give me enough idea to know what it is.

Thanks
Vivek

  parent reply	other threads:[~2017-12-07 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 23:10 [RFC PATCH] blk-throttle: add burst allowance Khazhismel Kumykov
2017-11-14 23:22 ` Khazhismel Kumykov
2017-11-16 16:50 ` Shaohua Li
2017-11-17  4:25   ` Khazhismel Kumykov
2017-11-17 19:26     ` Shaohua Li
2017-11-21  4:36       ` Khazhismel Kumykov
2017-12-07  0:41         ` Khazhismel Kumykov
2017-12-18 18:16         ` Khazhismel Kumykov
2017-12-18 18:29           ` Vivek Goyal
2017-12-18 20:39             ` Khazhismel Kumykov
2017-12-18 21:01               ` Vivek Goyal
2017-12-18 22:22                 ` Khazhismel Kumykov
2017-12-07 19:43   ` Vivek Goyal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-26 23:54 Khazhismel Kumykov

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=20171207194333.GB4067@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=axobe@kernel.dk \
    --cc=khazhy@google.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shli@fb.com \
    --cc=shli@kernel.org \
    --cc=tj@kernel.org \
    /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