From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: viktor.larionov@salva.ee,
device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools: scsi_id based path priorities and multiple prioritizers
Date: Sat, 18 May 2013 15:40:38 +0200 [thread overview]
Message-ID: <1368884438.26587.4.camel@lapoo.opensvc.com> (raw)
In-Reply-To: <51976d53.0c95dc0a.60df.0745SMTPIN_ADDED_BROKEN@mx.google.com>
>
> So, we poked up with code a bit, and wrote up a custom prioritizer,
> called sg_id. (patch for the latest multipath-tools available here:
> http://viktor.ee/multipath-tools-patches/sg_id_prio.patch)
>
Would the existing weightedpath work for you ?
> And so we’ve played another couple of our hours with multipath-tools
> code allowing it to accept multiple prioritizers in prio
> configuration. (patch here
> http://viktor.ee/multipath-tools-patches/multiprio.patch)
>
> In this case, prioritizers should be separated by coma, semicolon or
> space, and the end priority would be a sum of priorities given by all
> of the specified prioritizers. (a single prioritizer value is also
> accepted of course.)
>
> As an example:
>
> prio "sg_id, alua"
>
> prio_args "prio_sg_id(default)=0
> prio_sg_id(^[0-2]:0)=100"
>
> All comments are kindly welcome!
I personnaly find the multi-prioritizer feature interesting.
Let's hear other maintainers' comments ...
Best regards,
Christophe Varoqui
www.opensvc.com
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next parent reply other threads:[~2013-05-18 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51976d53.0c95dc0a.60df.0745SMTPIN_ADDED_BROKEN@mx.google.com>
2013-05-18 13:40 ` Christophe Varoqui [this message]
2013-05-18 21:53 ` multipath-tools: scsi_id based path priorities and multiple prioritizers Viktor Larionov
[not found] <001301ce53be$64265b10$2c731130$@larionov@salva.ee>
2013-05-21 14:19 ` Hannes Reinecke
2013-05-18 11:54 Viktor Larionov
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=1368884438.26587.4.camel@lapoo.opensvc.com \
--to=christophe.varoqui@gmail.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=viktor.larionov@salva.ee \
/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