From: Aaron Lu <aaron.lu@intel.com>
To: Gwendal Grignou <gwendal@google.com>, Lin Ming <minggr@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Change in sysfs topology for libata
Date: Thu, 20 Sep 2012 10:01:46 +0800 [thread overview]
Message-ID: <20120920020145.GA23210@mint-spring.sh.intel.com> (raw)
In-Reply-To: <CAMHSBOX416qXKpC_z_X+pfHs_Uo3Lw-JbjcwOFGYyKB1vdnW-w@mail.gmail.com>
On Wed, Sep 19, 2012 at 05:48:50PM -0700, Gwendal Grignou wrote:
> On Thu, Sep 13, 2012 at 8:38 AM, Lin Ming <minggr@gmail.com> wrote:
> > On Thu, Sep 13, 2012 at 4:07 AM, Gwendal Grignou <gwendal@google.com> wrote:
> >> [-Lin, +Lin]
> >
> > CC Aaron@Intel
Thanks Lin.
> > Could you show me what's the sysfs directory structure after libata
> > sysfs object melted into scsi sysfs objects?
>
> I am testing my patches, but the path to a block device will be as follow:
> /sys/device/pci0000:00/0000:00:06.0/0000:09:00.0/host0/port1/link1/dev1.0/target0:0:0/0:0:0:0/block/sda
>
> If you have a port multiplier, a disk behind it - port 4 of the pmp
> for instance:
> /sys/device/pci0000:00/0000:00:06.0/0000:09:00.0/host5/port6/link6.4/dev6.4.0/target5:4:0/5:4:0:0/block/sde
> while the port multiplier itself would be at
> /sys/device/pci0000:00/0000:00:06.0/0000:09:00.0/host5/port6/link6/dev6.0
>
> For reference, in a simple SAS topology, block device paths are like:
> /sys/device/pci0000:00/0000:00:08.0/0000:0b:00.0/host6/port-6:5/end_device-6:5/target6:0:5/6:0:5:0/block/sdg
>
> Does it make sense to you?
Looks good to me. I will test the code once you sent out, thanks.
And I think the following commit will no longer be needed once this
change is done:
commit ae0751ffc77e7f21629970fdab5528c573e637f8
[SCSI] add flag to skip the runtime PM calls on the host
-Aaron
next prev parent reply other threads:[~2012-09-20 2:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 20:02 Change in sysfs topology for libata Gwendal Grignou
2012-09-12 20:07 ` Gwendal Grignou
2012-09-13 15:38 ` Lin Ming
2012-09-20 0:48 ` Gwendal Grignou
2012-09-20 2:01 ` Aaron Lu [this message]
2012-09-27 19:04 ` [PATCH 0/3] Insert ATA transport objects in SCSI syfs topology Gwendal Grignou
2012-09-28 6:27 ` Aaron Lu
2012-10-01 18:22 ` Gwendal Grignou
2012-10-01 19:14 ` Dan Williams
2012-10-04 16:56 ` Gwendal Grignou
2012-10-07 23:13 ` Dan Williams
2012-09-27 19:04 ` [PATCH 1/3] Revert "ata: make ata port as parent device of scsi host" Gwendal Grignou
2012-09-29 17:08 ` Sergei Shtylyov
2012-10-01 18:22 ` Gwendal Grignou
2012-10-01 18:22 ` [PATCH 2/3] scsi: Allow devices to have arbitrary parent Gwendal Grignou
2012-10-01 18:22 ` [PATCH 3/3] libata: Change transport topology layout Gwendal Grignou
2012-09-27 19:04 ` [PATCH 2/3] scsi: Allow devices to have arbitrary parent Gwendal Grignou
2012-09-27 19:04 ` [PATCH 3/3] libata: Change transport topology layout Gwendal Grignou
2012-09-28 6:38 ` Aaron Lu
2012-10-04 0:49 ` Gwendal Grignou
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=20120920020145.GA23210@mint-spring.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=gwendal@google.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=minggr@gmail.com \
--cc=tj@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).