cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: brookxu <brookxu.cn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] blk-throtl: optimize IOPS throttle for large IO scenarios
Date: Tue, 27 Jul 2021 06:21:11 -1000	[thread overview]
Message-ID: <YQAydzEhZfPUpzWI@mtj.duckdns.org> (raw)
In-Reply-To: <34a6f4b5-9055-e519-5693-068f8dcb169c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hello,

On Tue, Jul 27, 2021 at 11:06:18AM +0800, brookxu wrote:
> Make blk-throttle use rq-qos may be more elegant. But I found that there may be at least
> one problem that is difficult to solve. blk-throttle supports separate throttle for read
> and write IOs, which means that we cannot suspend tasks during throttle, but rq-qos
> throttle IOs by suspending tasks.

Ah, right, I forgot about that.

> We may be able to relocate the blk-throttle hooks to the rq-qos hooks. Since we may not
> be able to replace the throttle hook, in this case, if we register a rq-qos to the system,
> part of the blk-throttle hooks is in rq-qos and part hooks not, which feels a bit confusing.
> In addition, we may need to implement more hooks, such as IO merge hook.

Would it be possible to just move the blk-throtl throttling hook right next
to the rq-qos hook so that it gets throttled after splitting?

Thanks.

-- 
tejun

  parent reply	other threads:[~2021-07-27 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  6:22 [PATCH] blk-throtl: optimize IOPS throttle for large IO scenarios brookxu
     [not found] ` <1626416569-30907-1-git-send-email-brookxu.cn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-07-16 16:09   ` Tejun Heo
2021-07-16 23:07     ` brookxu
     [not found]     ` <YPGvIzZUI+QxP1js-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2021-07-19 16:35       ` brookxu
     [not found]         ` <957ab14d-c4bc-32f0-3f7d-af98832ab955-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-07-26 21:46           ` Tejun Heo
     [not found]             ` <YP8tPwkJNMAcjDqk-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2021-07-27  3:06               ` brookxu
     [not found]                 ` <34a6f4b5-9055-e519-5693-068f8dcb169c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-07-27 16:21                   ` Tejun Heo [this message]
     [not found]                     ` <YQAydzEhZfPUpzWI-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2021-07-28  2:33                       ` brookxu
     [not found]                         ` <fab343e8-5929-fb30-90e3-b5b6bd34702a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-07-28  7:48                           ` 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=YQAydzEhZfPUpzWI@mtj.duckdns.org \
    --to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
    --cc=brookxu.cn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).