From: Hannes Reinecke <hare@suse.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: sekharan@linux.vnet.ibm.com,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH 2/2] Evaluate TGPS setting for device handler detection
Date: Tue, 21 Apr 2009 08:24:04 +0200 [thread overview]
Message-ID: <49ED6684.4080601@suse.de> (raw)
In-Reply-To: <49ECE046.6060109@cs.wisc.edu>
Hi Mike,
Mike Christie wrote:
> Chandra Seetharaman wrote:
>>> static const struct scsi_dh_devlist alua_dev_list[] = {
>>> - {"HP", "MSA VOLUME" },
>>> - {"HP", "HSV101" },
>>> - {"HP", "HSV111" },
>>> - {"HP", "HSV200" },
>>> - {"HP", "HSV210" },
>>> - {"HP", "HSV300" },
>>> - {"IBM", "2107900" },
>>> - {"IBM", "2145" },
>>> - {"Pillar", "Axiom" },
>>> - {"Intel", "Multi-Flex"},
>>> - {NULL, NULL}
>>> + {"", "", 3 },
>>> + {NULL, NULL, 0}
>>> };
>
> Is this going to make problems for the what the module alias patches
> were trying to do?
>
> Will userspace have to check for the mod alias stuff for scsi_dh_emc,
> scsi_dh_hp and scsh_dh_rdac, then for scsh_dh_alua does it check for the
> scsi devices sysfs tpgts file to see if ALUA is support?
Well, these patch actually precedes the modalias support, so obviously
we'll have to rework that to take everything (devtype, tpgs, vendor, model)
into account.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-04-21 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 8:06 [PATCH 2/2] Evaluate TGPS setting for device handler detection Hannes Reinecke
2009-03-19 10:43 ` Nicholas A. Bellinger
2009-04-16 16:30 ` Chandra Seetharaman
2009-04-20 20:51 ` Mike Christie
2009-04-21 6:24 ` Hannes Reinecke [this message]
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=49ED6684.4080601@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=pjones@redhat.com \
--cc=sekharan@linux.vnet.ibm.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).