linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] path_id: Re-introduce SAS phy enumeration of devices v2
Date: Tue, 03 Apr 2012 20:25:42 +0000	[thread overview]
Message-ID: <4F7B5CC6.5010108@suse.de> (raw)
In-Reply-To: <1333371414-412-1-git-send-email-nils.carlson@ericsson.com>

On 04/03/2012 08:24 PM, Kay Sievers wrote:
> On Tue, Apr 3, 2012 at 10:04, Nils Carlson <nils.carlson@ericsson.com> wrote:
> 
>> This patch reintroduces enumeration
>> of the form
>>
>> pci-0000:05:00.0-sas-phy0-0x500000e114de2b42:0-lun0
>>
>> where phy0 is the reintroduced substring where 0 corresponds
>> to the lowest phy identifier on the port to which the device
>> is connected.
> 
> Without having any real insight knowledge, a quick check:
> 
> We usually refuse any "find the lowest number approach" in new code,
> and require the kernel to export a stable instance number per parent
> device, which is entirely disconnected from any global device
> enumeration counter or prober ordering.
> 
> Almost all existing examples doing that are broken, and some even
> needed to be removed because they just blindly bet on luck that things
> are always in the same probe order.
> 
> Many device can individually unbound and rebound in the kernel, so
> after the rebind the same device will no longer have a smaller number
> like it had before. Kernel enumeration is only in a very few cases
> useful to build persistent paths.
> 
> The approach in this case is safe against individual pieces being
> unregistered and registered again?
> 
Note, this is just a first step towards real configuration.

This is the SAS PHY issue we've talked about earlier; eventually we'll
have to export paths for all phys.

I'm working on a patch (on top of this one), but it'll be quite a change
to path_id. So I've asked for this patch to be sent now, rather than
wait for the full blown solution.

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)

  parent reply	other threads:[~2012-04-03 20:25 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
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 [this message]
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=4F7B5CC6.5010108@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).