From: Hannes Reinecke <hare@suse.de>
To: Don Brace <Don.Brace@pmcs.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] hpsa: add in sas transport
Date: Wed, 21 Oct 2015 08:01:00 +0200 [thread overview]
Message-ID: <56272A1C.2050608@suse.de> (raw)
In-Reply-To: <07F70BBF6832E34FA1C923241E8833AB7CD46B3E@BBYEXM02.pmc-sierra.internal>
On 10/20/2015 10:07 PM, Don Brace wrote:
>> -----Original Message-----
>> From: Hannes Reinecke [mailto:hare@suse.de]
>> Sent: Wednesday, September 30, 2015 2:50 AM
>> To: Don Brace; linux-scsi@vger.kernel.org
>> Subject: Re: [PATCH] hpsa: add in sas transport
>>
>> On 09/30/2015 12:21 AM, Don Brace wrote:
>>> From: Kevin Barnett <kevin.barnett@pmcs.com>
>>>
>>> customers want lsscsi -t to show sas addresses when
>>> enumerating sas devices. The sas addresses are used
>>> mainly to light drive LEDs for location.
>>>
>>> Signed-off-by: Don Brace <don.brace@pmcs.com>
>>> ---
>>> drivers/scsi/hpsa.c | 704
>> ++++++++++++++++++++++++++++++++++++++++++-----
>>> drivers/scsi/hpsa.h | 37 ++
>>> drivers/scsi/hpsa_cmd.h | 14 +
>>> 3 files changed, 677 insertions(+), 78 deletions(-)
>>>
>>> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
>>> index 3b35de0..ae811a7 100644
>>> /* Notify scsi mid layer of any added devices */
>>> for (i = 0; i < nadded; i++) {
>>> - if (!(added[i]->expose_state & HPSA_SCSI_ADD))
>>> + if (!(added[i]->expose_device))
>>> continue;
>>> - if (scsi_add_device(sh, added[i]->bus,
>>> - added[i]->target, added[i]->lun) == 0)
>>> + if (hpsa_add_device(h, added[i]) == 0)
>>> continue;
>>> hpsa_show_dev_msg(KERN_WARNING, h, added[i],
>>> "addition failed, device not added.");
>> Sigh. Here we go again.
>>
>> I've probably asked you (or Mike Miller :-) about this several times
>> now, but couldn't you use the _real_ LUN addresses?
>>
>> Especially as you're now exposing 'real' devices, where is the point
>> of creating an internal LUN mapping table?
>>
>> If you were expose the devices with the actual LUN address (by eg
>> arranging the target/RAID controller on bus '0', the RAID devices on
>> bus '1', and the exposed devices on bus '2') you could remove the
>> internal LUN mapping table and quite some complexity would go away ...
>>
>
> This can be done.
>
> However, at this point, I do not want to change hpsa without more testing.
> I'll make another patch and send it up after it has a chance to be tested in our labs.
> Hope this is OK.
>
Sure. Just wanted to raise this (again :-), as I think it'd be a
good cleanup.
> I split out the other changes to separate patches as you recommended.
>
Please, go ahead.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (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:[~2015-10-21 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 22:21 [PATCH] hpsa update Don Brace
2015-09-29 22:21 ` [PATCH] hpsa: add in sas transport Don Brace
2015-09-30 7:49 ` Hannes Reinecke
2015-10-20 20:07 ` Don Brace
2015-10-21 6:01 ` 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=56272A1C.2050608@suse.de \
--to=hare@suse.de \
--cc=Don.Brace@pmcs.com \
--cc=linux-scsi@vger.kernel.org \
/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.