From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] path_id: Re-introduce SAS phy enumeration of devices
Date: Mon, 02 Apr 2012 13:35:09 +0000 [thread overview]
Message-ID: <4F79AB0D.9000100@suse.de> (raw)
In-Reply-To: <1333371414-412-1-git-send-email-nils.carlson@ericsson.com>
Hi Nils,
Thanks a lot for this. It definitely a step in the correct
direction. However, I have some comments to make:
On 04/02/2012 02:56 PM, Nils Carlson wrote:
> When path_id was converted to C code the enumeration of SAS
> devices by phy disappeared. This patch reintroduces enumeration
> of the form
>
> pci-0000:05:00.0-sas-phy0:1-0x500000e114de2b42:0-lun0
>
> where phy0:1 is the reintroduced substring where 0 corresponds
> to the lowest phy identifier on the port to which the device
> is connected and 1 is the number of phys on the port.
>
I would rather not do this.
First of all, I doubt we need the overall number of phys here.
Secondly, James B. assured me that the phy enumeration is pretty much
stable, so we should be able to use that number as-is.
Also, there is a 1:1 match between the 'phy_identifier' sysfs attribute
and the second number of the phy name itself (the first number is the
SCSI host number), so we could as well just parse the phy name and get
the number from there.
But, of course, reading the phy_identifier is okay, too.
So I would propose just to insert a 'phy1' there.
But again, thanks for doing it.
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)
next prev parent reply other threads:[~2012-04-02 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 12:56 [PATCH] path_id: Re-introduce SAS phy enumeration of devices Nils Carlson
2012-04-02 13:35 ` Hannes Reinecke [this message]
2012-04-02 13:55 ` Nils Carlson
2012-04-03 8:04 ` [PATCH] path_id: Re-introduce SAS phy enumeration of devices v2 Nils Carlson
2012-04-03 18:24 ` Kay Sievers
2012-04-03 20:25 ` Hannes Reinecke
2012-04-03 21:23 ` Kay Sievers
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=4F79AB0D.9000100@suse.de \
--to=hare@suse.de \
--cc=linux-hotplug@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 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).