[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0e03867e-54ea-fb10-1f8a-f098c9dbb026@bytedance.com>
Date: Thu, 12 Jan 2023 11:26:42 +0800
From: hanjinke <hanjinke.666@...edance.com>
To: Michal Koutný <mkoutny@...e.com>,
Tejun Heo <tj@...nel.org>
Cc: Jan Kara <jack@...e.cz>, josef@...icpanda.com, axboe@...nel.dk,
cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, yinxin.x@...edance.com
Subject: Re: [External] Re: [PATCH v3] blk-throtl: Introduce sync and async
queues for blk-throtl
在 2023/1/11 下午8:35, Michal Koutný 写道:
> Hello.
>
> Thanks all for sharing ideas and more details (in time-previous messages).
>
> On Sat, Jan 07, 2023 at 02:07:38AM +0800, hanjinke <hanjinke.666@...edance.com> wrote:
>> But for some specific scenarios with old kernel versions, blk-throtl
>> is alose needed. The scenario described in my email is in the early stage of
>> research and extensive testing for it. During this period,some priority
>> inversion issues amoug cgroups or within one cgroup have been observed. So I
>> send this patch to try to fix or mitigate some of these issues.
>
> Jinke, do you combine blk-throtl with memory limits? (As that could in theory
> indirectly reduce async requests as dirtier would be slowed down.)
>
Hi
In fact, some of those tests above are done in vm with only total 16g
memory.
Agree with what you said, if we further tighten the memory usage, things
will get better because this will indirectly reduces writeback pages in
blk-throtl queue.
Thanks.
Powered by blists - more mailing lists