From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: DM-DEVEL ML <dm-devel@redhat.com>, Martin Wilck <mwilck@suse.com>,
Khazhismel Kumykov <khazhy@google.com>
Subject: Re: [PATCH] multipath-tools: add info to man page for the historical-service-time path selector
Date: Tue, 07 Jul 2020 17:44:01 -0400 [thread overview]
Message-ID: <877dvfm25a.fsf@collabora.com> (raw)
In-Reply-To: <20200707211758.12528-1-xose.vazquez@gmail.com> (Xose Vazquez Perez's message of "Tue, 7 Jul 2020 23:17:58 +0200")
Xose Vazquez Perez <xose.vazquez@gmail.com> writes:
> Cc: Khazhismel Kumykov <khazhy@google.com>
> Cc: Gabriel Krisman Bertazi <krisman@collabora.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@redhat.com>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
> multipath/multipath.conf.5 | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
> index 05a5e8ff..6e637769 100644
> --- a/multipath/multipath.conf.5
> +++ b/multipath/multipath.conf.5
> @@ -205,6 +205,10 @@ of outstanding I/O to the path.
> (Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on the amount
> of outstanding I/O to the path and its relative throughput.
> .TP
> +.I "historical-service-time 0"
> +(Since 5.8 kernel) Choose the path for the next bunch of I/O based on the shortest
> +time by comparing estimated service time (based on historical service
> time).
Hi,
Thanks for doing this.
What about:
Choose the path for the next bunch of IOs through an estimation of
future service time based on the history of previous I/O submitted to
each path, in an attempt to maximize throughput. A path's service-time
is loosely defined as the time between an IO start and its completion
and is updated through an exponential moving average (EMA) of the
historical service time of each path.
> +.TP
> The default is: \fBservice-time 0\fR
It supports some parameters, shouldn't they be documented here? Some
explanation for the parameters exists in hst_create() in the kernel
/*
* Arguments: [<base_weight> [<threshold_multiplier>]]
* <base_weight>: Base weight for ema [0, 1024) 10-bit fixed point. A
* value of 0 will completely ignore any history.
* If not given, default (HST_FIXED_95) is used.
* <threshold_multiplier>: Minimum threshold multiplier for paths to
* be considered different. That is, a path is
* considered different iff (p1 > N * p2) where p1
* is the path with higher service time. A threshold
* of 1 or 0 has no effect. Defaults to 0.
*/
> .RE
> .
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2020-07-07 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 21:17 [PATCH] multipath-tools: add info to man page for the historical-service-time path selector Xose Vazquez Perez
2020-07-07 21:44 ` Gabriel Krisman Bertazi [this message]
2020-07-07 23:55 ` Martin Wilck
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=877dvfm25a.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=dm-devel@redhat.com \
--cc=khazhy@google.com \
--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.