From: James Bottomley <James.Bottomley@suse.de>
To: Tejun Heo <tj@kernel.org>
Cc: Herbert Poetzl <herbert@13thfloor.at>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: PMP and SEMB messages to SEP
Date: Mon, 17 Jan 2011 11:21:46 -0600 [thread overview]
Message-ID: <1295284906.3015.136.camel@mulgrave.site> (raw)
In-Reply-To: <20110117171836.GI27123@htj.dyndns.org>
On Mon, 2011-01-17 at 18:18 +0100, Tejun Heo wrote:
> Hello, James.
>
> On Mon, Jan 17, 2011 at 10:18:51AM -0600, James Bottomley wrote:
> > > The problem is that the PMP device itself is currently not allocated a
> > > userland visible device, so it doesn't have any /dev/* node. Hmmm...
> >
> > So perhaps it should be. If you look at the equivalent topology on SAS,
> > our expanders have a bsg device node precisely so that we can do this.
> >
> > That said, SAS expanders have a defined protocol (SAS Management
> > Protocol) to talk to the outside world, so they are real visible objects
> > always in our topology ... I'm not sure PMP has this ... it seems that
> > all PMP visibility is an extension to the standard?
>
> SATA PMP is mostly a dumb switch and there isn't much which can be
> done by issuing custom commands (and IIRC we didn't have bsg back
> then), so it was never made visible to userland, but yeah probably
> exporting a bsg node is a good idea. Inside libata, the PMP device
> has its device representation and all so it shouldn't be too difficult
> either. Not really sure how the inquiry and stuff should be handled
> tho.
Expanders aren't SCSI devices either ... that means they don't appear as
visible to standard SCSI mechanisms like INQUIRY (SMP isn't a SCSI
protocol it's a SAS extension). They just appear as part of the
topology in the device tree.
James
next prev parent reply other threads:[~2011-01-17 17:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 19:25 PMP and SEMB messages to SEP Herbert Poetzl
2011-01-14 14:20 ` Tejun Heo
2011-01-14 16:59 ` Herbert Poetzl
2011-01-14 17:04 ` Tejun Heo
2011-01-14 17:37 ` Herbert Poetzl
2011-01-17 15:40 ` Tejun Heo
2011-01-17 16:18 ` James Bottomley
2011-01-17 17:13 ` Herbert Poetzl
2011-01-17 17:20 ` Tejun Heo
2011-01-17 17:34 ` Herbert Poetzl
2011-01-17 17:39 ` Tejun Heo
2011-01-17 17:48 ` Herbert Poetzl
2011-01-17 18:05 ` James Bottomley
2011-01-17 18:21 ` Herbert Poetzl
2011-01-17 18:27 ` Herbert Poetzl
2011-01-17 17:18 ` Tejun Heo
2011-01-17 17:21 ` James Bottomley [this message]
2011-01-17 17:24 ` Tejun Heo
2011-01-25 3:07 ` Herbert Poetzl
2011-01-25 14:14 ` James Bottomley
2011-04-03 17:39 ` Herbert Poetzl
2011-04-03 18:38 ` James Bottomley
2011-01-17 18:55 ` Jeff Garzik
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=1295284906.3015.136.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=herbert@13thfloor.at \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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).