From: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: [PATCH v2] multipath-tools: add availability of service-time and queue-length to multipath.conf.5
Date: Tue, 21 Feb 2017 22:31:08 +0100 [thread overview]
Message-ID: <20170221213108.4126-1-xose.vazquez@gmail.com> (raw)
https://kernelnewbies.org/Linux_2_6_31#head-7a4afa809f53cf9a2df884c745f4f8150e24645a
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
---
v2 - remove XXX tags
---
multipath/multipath.conf.5 | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
index 7de8bc7..4961c06 100644
--- a/multipath/multipath.conf.5
+++ b/multipath/multipath.conf.5
@@ -166,14 +166,12 @@ Loop through every path in the path group, sending the same amount of I/O to
each. Some aspects of behavior can be controlled with the attributes:
\fIrr_min_io\fR, \fIrr_min_io_rq\fR and \fIrr_weight\fR.
.TP
-.\" XXX
.I "queue-length 0"
-(Since ??? kernel) Choose the path for the next bunch of I/O based on the amount
+(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.
.TP
-.\" XXX
.I "service-time 0"
-(Since ??? kernel) Choose the path for the next bunch of I/O based on the amount
+(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
The default is: \fBservice-time 0\fR
--
2.11.1
next reply other threads:[~2017-02-21 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 21:31 Xose Vazquez Perez [this message]
2017-02-27 5:46 ` [PATCH v2] multipath-tools: add availability of service-time and queue-length to multipath.conf.5 Christophe Varoqui
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=20170221213108.4126-1-xose.vazquez@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=dm-devel@redhat.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.