From: Alasdair G Kergon <agk@redhat.com>
To: Hannes Reinecke <hare@suse.de>,
device-mapper development <dm-devel@redhat.com>,
James Bottomley <jbottomley@parallels.com>,
Mike Snitzer <snitzer@redhat.com>,
linux-scsi@vger.kernel.org
Subject: Re: [dm-devel] [RESEND PATCH 2/3] dm mpath: add 'default_hw_handler' feature
Date: Wed, 11 Jul 2012 11:27:54 +0100 [thread overview]
Message-ID: <20120711102754.GA2095@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4FEAA557.7050501@suse.de>
On Wed, Jun 27, 2012 at 08:16:55AM +0200, Hannes Reinecke wrote:
> On 06/26/2012 08:32 PM, Mike Snitzer wrote:
> > When specifying the feature 'default_hw_handler' multipath will use
> > the currently attached hardware handler instead of trying to attach the
> > one specified during table load. If no hardware handler is attached the
> > specified hardware handler will be used.
> >
> > Leverages scsi_dh_attach's ability to increment the scsi_dh's reference
> > count if the same scsi_dh name is provided when attaching -- currently
> > attached scsi_dh name is determined with scsi_dh_attached_handler_name.
> >
> > Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> > Tested-by: Babu Moger <babu.moger@netapp.com>
> > Reviewed-by: Chandra Seetharaman <sekharan@us.ibm.com>
> Looks good.
Maybe, but I'd like to see an inline explanation of what this confusing new
setting means and a better patch header that provides some motivation for this
change.
To my eyes, the word "default" is over-used here. If I *don't* specify the new
"default" flag, surely I'll get default behaviour, won't I, by definition? And
if I do specify it, I'm asking for default behaviour too, so isn't it
redundant?
Alasdair
next prev parent reply other threads:[~2012-07-11 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 18:32 [RESEND PATCH 0/3] multipath features for 3.6 Mike Snitzer
2012-06-26 18:32 ` [RESEND PATCH 1/3] scsi_dh: add scsi_dh_attached_handler_name Mike Snitzer
2012-07-02 21:07 ` Mike Snitzer
2012-06-26 18:32 ` [RESEND PATCH 2/3] dm mpath: add 'default_hw_handler' feature Mike Snitzer
2012-06-27 6:16 ` [dm-devel] " Hannes Reinecke
2012-07-11 10:27 ` Alasdair G Kergon [this message]
2012-07-11 13:20 ` Mike Snitzer
2012-06-26 18:32 ` [RESEND PATCH 3/3] dm mpath: add ability to disable partition creation Mike Snitzer
2012-07-11 15:18 ` [dm-devel] " Alasdair G Kergon
2012-07-25 12:02 ` Hannes Reinecke
2012-07-26 17:03 ` Benjamin Marzinski
2012-07-27 14:00 ` [dm-devel] " Hannes Reinecke
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=20120711102754.GA2095@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).