All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Martin Wilck <mwilck@suse.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	DM_DEVEL-ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH v3 5/8] multipath-tools: clarify path selector descriptions in multipath.conf.5
Date: Thu, 18 Jun 2026 15:38:16 -0400	[thread overview]
Message-ID: <ajRJKF_oQ9ws3HeR@redhat.com> (raw)
In-Reply-To: <20260618134521.16878-1-xose.vazquez@gmail.com>

On Thu, Jun 18, 2026 at 03:45:20PM +0200, Xose Vazquez Perez wrote:
> Selectors operate on the next individual I/O request rather
> than a "bunch" of I/O.
> 
> Suggested-by: Benjamin Marzinski <bmarzins@redhat.com>
> Cc: Martin Wilck <mwilck@suse.com>
> Cc: Benjamin Marzinski <bmarzins@redhat.com>
> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> Cc: DM_DEVEL-ML <dm-devel@lists.linux.dev>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
> v2: fix typo, s/group/groups (spotted by Martin)
> v3: revert v2, "group" makes more sense. (spotted by Ben)

Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>

> 
>  multipath/multipath.conf.5.in | 12 +++++-------
>  1 file changed, 5 insertions(+), 7 deletions(-)
> 
> diff --git a/multipath/multipath.conf.5.in b/multipath/multipath.conf.5.in
> index 422ab120..5b730801 100644
> --- a/multipath/multipath.conf.5.in
> +++ b/multipath/multipath.conf.5.in
> @@ -2,7 +2,7 @@
>  .\" Update the date below if you make any significant change.
>  .\" ----------------------------------------------------------------------------
>  .
> -.TH MULTIPATH.CONF 5 2026-05-27 Linux
> +.TH MULTIPATH.CONF 5 2026-06-13 Linux
>  .
>  .
>  .\" ----------------------------------------------------------------------------
> @@ -193,20 +193,18 @@ kernel multipath target:
>  .RS
>  .TP
>  .I "round-robin 0"
> -Choose the path for the next bunch of I/O by looping through every path in the
> -path group, sending \fBthe same number of I/O requests\fR to each path.
> -
> +Choose the path for the next I/O request by \fBcycling through the path group\fR.
>  .TP
>  .I "queue-length 0"
> -(Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on \fBthe lowest
> +(Since 2.6.31 kernel) Choose the path for the next I/O request based on \fBthe lowest
>  number of outstanding in-flight I/O requests\fR to the path.
>  .TP
>  .I "service-time 0"
> -(Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on \fBthe
> +(Since 2.6.31 kernel) Choose the path for the next I/O request based on \fBthe
>  lowest total size (in bytes) of outstanding in-flight I/O requests\fR to the path.
>  .TP
>  .I "historical-service-time 0"
> -(Since 5.8 kernel) Choose the path for the next bunch of I/O with \fBa dynamic
> +(Since 5.8 kernel) Choose the path for the next I/O request with \fBa dynamic
>  algorithm based on the historical service time and the number of outstanding
>  in-flight I/O requests\fR to the path.
>  .TP
> -- 
> 2.54.0


      reply	other threads:[~2026-06-18 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 13:45 [PATCH v3 5/8] multipath-tools: clarify path selector descriptions in multipath.conf.5 Xose Vazquez Perez
2026-06-18 19:38 ` Benjamin Marzinski [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=ajRJKF_oQ9ws3HeR@redhat.com \
    --to=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=mwilck@suse.com \
    --cc=xose.vazquez@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.