From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>,
"Nalla, Ravikanth" <ravikanth.nalla@hpe.com>
Subject: Re: [dm-devel] [PATCH v2] dm pref-path: provides preferred path load balance policy
Date: Sat, 30 Jan 2016 17:32:28 -0600 [thread overview]
Message-ID: <20160130233228.GF24960@octiron.msp.redhat.com> (raw)
In-Reply-To: <20160130202525.GE24960@octiron.msp.redhat.com>
On Sat, Jan 30, 2016 at 02:25:25PM -0600, Benjamin Marzinski wrote:
> Before this commit, it always used the pref bit. Again, like I said
> before, I'm saying that this was the wrong thing to do. The Spec is
Oops. I meant: "I'm NOT saying that this was the wrong thing to do".
I am also fine with changing the default back to making the pref bit
always create it's own path group. As long there is a way for users to
get either behavior, I'm happy.
-Ben
> pretty vague on what you should expect to happen when you set to pref
> bit. When the path was in a group by itself, I got complaints. Now that
> the path is is a group with other active/optimized paths, I get
> complaints. The only answer is to allow the user to say what they want
> the pref bit to mean.
>
> -Ben
next prev parent reply other threads:[~2016-01-30 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 13:31 [PATCH v2] dm pref-path: provides preferred path load balance policy Ravikanth Nalla
2016-01-22 13:42 ` Hannes Reinecke
2016-01-22 16:59 ` Mike Snitzer
2016-01-22 16:59 ` Mike Snitzer
2016-01-29 14:10 ` Nalla, Ravikanth
2016-01-29 14:10 ` Nalla, Ravikanth
2016-01-29 17:50 ` Benjamin Marzinski
2016-01-30 8:32 ` Hannes Reinecke
2016-01-30 20:25 ` Benjamin Marzinski
2016-01-30 23:32 ` Benjamin Marzinski [this message]
2016-01-22 17:06 ` [dm-devel] " Benjamin Marzinski
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=20160130233228.GF24960@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ravikanth.nalla@hpe.com \
--cc=snitzer@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.