Linux block layer
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Jinke Han <hanjinke.666@bytedance.com>
Cc: tj@kernel.org, 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: [RESEND PATCH v6] blk-throtl: Introduce sync and async queues for blk-throtl
Date: Mon, 6 Mar 2023 18:06:34 +0100	[thread overview]
Message-ID: <20230306170634.os744umla72yoryw@blackpad> (raw)
In-Reply-To: <20230228085935.71465-1-hanjinke.666@bytedance.com>

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

Hello Jinke.

On Tue, Feb 28, 2023 at 04:59:35PM +0800, Jinke Han <hanjinke.666@bytedance.com> wrote:
> and gives a huge priority to sync write ios. Sync queue only make sense
> for write ios as we treat all read io as sync io.
[...]
> +/* For write ios, dispatch 4 sync ios and 1 normal io in one loop */
> +#define THROTL_SYNC_FACTOR 4

This looks like an unexplained number wired in.
E.g. I'd expect that 1st iteration would have this factor==1, i.e. RR
between sync and async queue.

What is the reason for this value? E.g. I assume it'd depend on number
of synchronous writers and flusher threads and their activity, i.e.
could you describe why this value caters the best for wide range of
various sync and async situations? Or add a comment what is the
particular value based on (so that it can be reassessed should those
dependencies change in the future).

Thanks,
Michal

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-03-06 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  8:59 [RESEND PATCH v6] blk-throtl: Introduce sync and async queues for blk-throtl Jinke Han
2023-03-06 17:06 ` Michal Koutný [this message]

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=20230306170634.os744umla72yoryw@blackpad \
    --to=mkoutny@suse.com \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=hanjinke.666@bytedance.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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