From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
To: Josef Bacik <josef@toxicpanda.com>,
axboe@kernel.dk, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org, tj@kernel.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
kernel-team@fb.com
Cc: Josef Bacik <jbacik@fb.com>
Subject: Re: [PATCH 13/14] Documentation: add a doc for blk-iolatency
Date: Sun, 5 Aug 2018 15:40:16 +0300 [thread overview]
Message-ID: <30471358-6482-1e3f-e8bc-4195289d4108@yandex-team.ru> (raw)
In-Reply-To: <20180703151503.2549-14-josef@toxicpanda.com>
On 03.07.2018 18:15, Josef Bacik wrote:
> From: Josef Bacik <jbacik@fb.com>
>
> A basic documentation to describe the interface, statistics, and
> behavior of io.latency.
>
Request size also has significant effect on latency of following requests.
It's worth to notice that smaller max_sectors_kb gives more control over latency.
> Signed-off-by: Josef Bacik <jbacik@fb.com>
> ---
> Documentation/admin-guide/cgroup-v2.rst | 79 +++++++++++++++++++++++++++++++++
> 1 file changed, 79 insertions(+)
>
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> index 8a2c52d5c53b..569ce27b85e5 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -51,6 +51,9 @@ v1 is available under Documentation/cgroup-v1/.
> 5-3. IO
> 5-3-1. IO Interface Files
> 5-3-2. Writeback
> + 5-3-3. IO Latency
> + 5-3-3-1. How IO Latency Throttling Works
> + 5-3-3-2. IO Latency Interface Files
> 5-4. PID
> 5-4-1. PID Interface Files
> 5-5. Device
> @@ -1446,6 +1449,82 @@ writeback as follows.
> vm.dirty[_background]_ratio.
>
>
> +IO Latency
> +~~~~~~~~~~
> +
> +This is a cgroup v2 controller for IO workload protection. You provide a group
> +with a latency target, and if the average latency exceeds that target the
> +controller will throttle any peers that have a lower latency target than the
> +protected workload.
> +
> +The limits are only applied at the peer level in the hierarchy. This means that
> +in the diagram below, only groups A, B, and C will influence each other, and
> +groups D and F will influence each other. Group G will influence nobody.
> +
> + [root]
> + / | \
> + A B C
> + / \ |
> + D F G
> +
> +
> +So the ideal way to configure this is to set io.latency in groups A, B, and C.
> +Generally you do not want to set a value lower than the latency your device
> +supports. Experiment to find the value that works best for your workload.
> +Start at higher than the expected latency for your device and watch the
> +total_lat_avg value in io.stat for your workload group to get an idea of the
> +latency you see during normal operation. Use this value as a basis for your
> +real setting, setting at 10-15% higher than the value in io.stat.
> +Experimentation is key here because total_lat_avg is a running total, so is the
> +"statistics" portion of "lies, damned lies, and statistics."
> +
> +How IO Latency Throttling Works
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +io.latency is work conserving; so as long as everybody is meeting their latency
> +target the controller doesn't do anything. Once a group starts missing its
> +target it begins throttling any peer group that has a higher target than itself.
> +This throttling takes 2 forms:
> +
> +- Queue depth throttling. This is the number of outstanding IO's a group is
> + allowed to have. We will clamp down relatively quickly, starting at no limit
> + and going all the way down to 1 IO at a time.
> +
> +- Artificial delay induction. There are certain types of IO that cannot be
> + throttled without possibly adversely affecting higher priority groups. This
> + includes swapping and metadata IO. These types of IO are allowed to occur
> + normally, however they are "charged" to the originating group. If the
> + originating group is being throttled you will see the use_delay and delay
> + fields in io.stat increase. The delay value is how many microseconds that are
> + being added to any process that runs in this group. Because this number can
> + grow quite large if there is a lot of swapping or metadata IO occurring we
> + limit the individual delay events to 1 second at a time.
> +
> +Once the victimized group starts meeting its latency target again it will start
> +unthrottling any peer groups that were throttled previously. If the victimized
> +group simply stops doing IO the global counter will unthrottle appropriately.
> +
> +IO Latency Interface Files
> +~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> + io.latency
> + This takes a similar format as the other controllers.
> +
> + "MAJOR:MINOR target=<target time in microseconds"
> +
> + io.stat
> + If the controller is enabled you will see extra stats in io.stat in
> + addition to the normal ones.
> +
> + depth
> + This is the current queue depth for the group.
> +
> + avg_lat
> + The running average IO latency for this group in microseconds.
> + Running average is generally flawed, but will give an
> + administrator a general idea of the overall latency they can
> + expect for their workload on the given disk.
> +
> PID
> ---
>
>
next prev parent reply other threads:[~2018-08-05 12:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 15:14 [PATCH 0/14][V6] Introduce io.latency io controller for cgroups Josef Bacik
2018-07-03 15:14 ` [PATCH 01/14] block: add bi_blkg to the bio " Josef Bacik
2018-07-03 15:14 ` [PATCH 02/14] block: introduce bio_issue_as_root_blkg Josef Bacik
2018-07-03 15:14 ` [PATCH 03/14] blk-cgroup: allow controllers to output their own stats Josef Bacik
2018-07-03 15:14 ` [PATCH 04/14] blk: introduce REQ_SWAP Josef Bacik
2018-07-03 15:14 ` [PATCH 05/14] swap,blkcg: issue swap io with the appropriate context Josef Bacik
2018-07-03 19:27 ` Randy Dunlap
2018-07-03 19:32 ` Jens Axboe
2018-07-03 15:14 ` [PATCH 06/14] blkcg: add generic throttling mechanism Josef Bacik
2018-08-05 12:41 ` Konstantin Khlebnikov
2018-07-03 15:14 ` [PATCH 07/14] memcontrol: schedule throttling if we are congested Josef Bacik
2018-07-03 15:14 ` [PATCH 08/14] blk-stat: export helpers for modifying blk_rq_stat Josef Bacik
2018-07-03 15:14 ` [PATCH 09/14] blk-rq-qos: refactor out common elements of blk-wbt Josef Bacik
2018-07-03 15:14 ` [PATCH 10/14] block: remove external dependency on wbt_flags Josef Bacik
2018-07-03 15:15 ` [PATCH 11/14] rq-qos: introduce dio_bio callback Josef Bacik
2018-07-03 19:29 ` Randy Dunlap
2018-07-03 19:33 ` Jens Axboe
2018-07-03 15:15 ` [PATCH 12/14] block: introduce blk-iolatency io controller Josef Bacik
2018-07-03 19:32 ` Randy Dunlap
2018-07-03 15:15 ` [PATCH 13/14] Documentation: add a doc for blk-iolatency Josef Bacik
2018-07-03 22:28 ` Randy Dunlap
2018-08-05 12:40 ` Konstantin Khlebnikov [this message]
2018-07-03 15:15 ` [PATCH 14/14] skip readahead if the cgroup is congested Josef Bacik
2018-07-03 15:37 ` [PATCH 0/14][V6] Introduce io.latency io controller for cgroups Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2018-06-29 19:25 [PATCH 00/14][V5] " Josef Bacik
2018-06-29 19:25 ` [PATCH 13/14] Documentation: add a doc for blk-iolatency Josef Bacik
2018-07-02 21:49 ` Tejun Heo
2018-06-27 19:09 [PATCH 00/14][V4] Introduce io.latency io controller for cgroups Josef Bacik
2018-06-27 19:09 ` [PATCH 13/14] Documentation: add a doc for blk-iolatency Josef Bacik
2018-06-27 23:59 ` Randy Dunlap
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=30471358-6482-1e3f-e8bc-4195289d4108@yandex-team.ru \
--to=khlebnikov@yandex-team.ru \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hannes@cmpxchg.org \
--cc=jbacik@fb.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).