mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hanjinke <hanjinke.666@bytedance.com>
To: Tejun Heo <tj@kernel.org>, Jan Kara <jack@suse.cz>
Cc: "Michal Koutný" <mkoutny@suse.com>,
	josef@toxicpanda.com, axboe@kernel.dk, cgroups@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	yinxin.x@bytedance.com
Subject: Re: [External] Re: [PATCH v3] blk-throtl: Introduce sync and async queues for blk-throtl
Date: Sat, 7 Jan 2023 02:07:38 +0800	[thread overview]
Message-ID: <c839ba6c-80ac-6d92-af64-5c0e1956ae93@bytedance.com> (raw)
In-Reply-To: <Y7hTHZQYsCX6EHIN@slm.duckdns.org>



在 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

  reply	other threads:[~2023-01-06 18:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 13:05 Jinke Han
2022-12-26 15:24 ` kernel test robot
2023-01-04 22:11 ` Tejun Heo
2023-01-05  7:28   ` [External] " hanjinke
2023-01-05 16:18 ` Michal Koutný
2023-01-05 17:35   ` Tejun Heo
2023-01-05 19:22     ` Michal Koutný
2023-01-05 21:39       ` Tejun Heo
2023-01-06 15:38   ` Jan Kara
2023-01-06 16:58     ` Tejun Heo
2023-01-06 18:07       ` hanjinke [this message]
2023-01-06 18:15         ` [External] " Tejun Heo
2023-01-07  4:44           ` hanjinke
2023-01-09 18:08             ` Tejun Heo
2023-01-10 13:07               ` hanjinke
2023-01-11 12:35         ` Michal Koutný
2023-01-12  3:26           ` hanjinke
2023-01-09 10:59       ` Jan Kara
2023-01-09 17:10         ` Tejun Heo

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=c839ba6c-80ac-6d92-af64-5c0e1956ae93@bytedance.com \
    --to=hanjinke.666@bytedance.com \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=tj@kernel.org \
    --cc=yinxin.x@bytedance.com \
    /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
all inboxes | Powered by JetHome®