[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c839ba6c-80ac-6d92-af64-5c0e1956ae93@bytedance.com>
Date: Sat, 7 Jan 2023 02:07:38 +0800
From: hanjinke <hanjinke.666@...edance.com>
To: Tejun Heo <tj@...nel.org>, Jan Kara <jack@...e.cz>
Cc: Michal Koutný <mkoutny@...e.com>,
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/7 上午12:58, Tejun Heo 写道:
>
> Jinke, is the case you described in the original email what you actually saw
> in production or a simplified test case for demonstration? If the latter,
> can you describe actual problems seen in production?
>
> Thanks.
>
Hi
In our internal scenario, iocost has been deployed as the main io
isolation method and is gradually spreading。
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.
Thanks
Jinke
Powered by blists - more mailing lists