dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: dm-devel@redhat.com
Subject: Re: [PATCH 3/4] scsi_dh_rdac: Adding the match function for	rdac device handler
Date: Wed, 02 Nov 2011 08:20:31 +0100	[thread overview]
Message-ID: <4EB0EF3F.1010300@suse.de> (raw)
In-Reply-To: <47D23AD8469A2B448F33C24BD7A39BD9105DB4D8@RTPMVEXC1-PRD.hq.netapp.com>

On 11/01/2011 06:19 PM, Moger, Babu wrote:
> This patch introduces the match function for rdac device handler. Without this,
> sometimes handler attach fails during the device_add.  The match function was
> introduced by this patch
> http://www.spinics.net/lists/linux-scsi/msg54284.html
>
> Signed-off-by: Babu Moger<babu.moger@netapp.com>
> ---
>
> --- linux/drivers/scsi/device_handler/scsi_dh_rdac.c.orig	2011-10-31 11:25:44.000000000 -0500
> +++ linux/drivers/scsi/device_handler/scsi_dh_rdac.c	2011-10-31 11:31:34.000000000 -0500
> @@ -819,6 +819,21 @@ static const struct scsi_dh_devlist rdac
>   	{NULL, NULL},
>   };
>
> +static bool rdac_match(struct scsi_device *sdev)
> +{
> +	int i;
> +
> +	for (i = 0; rdac_dev_list[i].vendor; i++) {
> +		if (!strncmp(sdev->vendor, rdac_dev_list[i].vendor,
> +			strlen(rdac_dev_list[i].vendor))&&
> +		    !strncmp(sdev->model, rdac_dev_list[i].model,
> +			strlen(rdac_dev_list[i].model))) {
> +			return true;
> +		}
> +	}
> +	return false;
> +}
> +
>   static int rdac_bus_attach(struct scsi_device *sdev);
>   static void rdac_bus_detach(struct scsi_device *sdev);
>
> @@ -831,6 +846,7 @@ static struct scsi_device_handler rdac_d
>   	.attach = rdac_bus_attach,
>   	.detach = rdac_bus_detach,
>   	.activate = rdac_activate,
> +	.match = rdac_match,
>   };
>
>   static int rdac_bus_attach(struct scsi_device *sdev)
>
As stated in the other mail, I guess we would need to have a check 
if the LUN is in ALUA mode.
And, btw, the _original_ intention was to allow vendor-specific 
device_handler to do some better probing, eg querying some 
vendor-specific VPD pages.
Especially for RDAC it would make far more sense to query the 
existence and format of one of the RDAC-specific VPD pages (eg 0xC2, 
0xC4, or 0xC8) and use that for matching.
Then you could do away with the vendor/model array altogether here 
and we wouldn't need to update the rdac handler every time a new 
array comes out or has been rebranded by some OEM.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2011-11-02  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 17:19 [PATCH 3/4] scsi_dh_rdac: Adding the match function for rdac device handler Moger, Babu
2011-11-02  7:20 ` Hannes Reinecke [this message]
2011-11-02 15:23   ` [dm-devel] " Moger, Babu
2011-11-02 15:33     ` Hannes Reinecke
2011-11-02 15:41       ` Moger, Babu
2011-11-02 15:46     ` Mike Snitzer
2011-11-03 14:47       ` [dm-devel] " Moger, Babu
2011-11-03 15:17         ` Mike Snitzer
2011-11-16 17:32           ` Mike Snitzer
2011-11-16 22:10             ` Moger, Babu
2011-11-16 22:40               ` Mike Snitzer

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=4EB0EF3F.1010300@suse.de \
    --to=hare@suse.de \
    --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 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).