[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1f98f78-bf01-272f-3121-02612d01d57e@infradead.org>
Date: Tue, 3 Jul 2018 12:32:12 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Josef Bacik <josef@...icpanda.com>, axboe@...nel.dk,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
hannes@...xchg.org, tj@...nel.org, linux-fsdevel@...r.kernel.org,
linux-block@...r.kernel.org, kernel-team@...com
Cc: Josef Bacik <jbacik@...com>
Subject: Re: [PATCH 12/14] block: introduce blk-iolatency io controller
On 07/03/2018 08:15 AM, Josef Bacik wrote:
> diff --git a/block/Kconfig b/block/Kconfig
> index 28ec55752b68..074c6099c31f 100644
> --- a/block/Kconfig
> +++ b/block/Kconfig
> @@ -149,6 +149,18 @@ config BLK_WBT
> dynamically on an algorithm loosely based on CoDel, factoring in
> the realtime performance of the disk.
>
> +config BLK_CGROUP_IOLATENCY
> + bool "Enable support for latency based cgroup IO protection"
> + depends on BLK_CGROUP=y
> + default n
> + ---help---
> + Enabling this option enables the .latency interface for IO throttling.
> + The IO controller will attempt to maintain average IO latencies below
> + the configured latency target, throttling anybody with a higher latency
Could that be: any process {or any task}
I don't want to see it throttling any bodies.
> + target than the victimized group.
> +
> + Note, this is an experimental interface and could be changed someday.
> +
> config BLK_WBT_SQ
> bool "Single queue writeback throttling"
> default n
--
~Randy
Powered by blists - more mailing lists