From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Grant Grundler <grundler@google.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] 2.6.27-rc2 SCSI Rewrite help text for SCSI_SAS_HOST_SMP
Date: Tue, 12 Aug 2008 16:46:47 -0500 [thread overview]
Message-ID: <1218577607.3549.57.camel@localhost.localdomain> (raw)
In-Reply-To: <da824cf30808121435x7782a440v65f919010372e7a8@mail.gmail.com>
On Tue, 2008-08-12 at 14:35 -0700, Grant Grundler wrote:
> Rewrite libsas/Kconfig help text for SCSI_SAS_HOST_SMP option.
> Previous text is useless. Thanks for Martin Petersen (mkp) for pointing
> me in the right direction.
>
> Signed-off-By: Grant Grundler <grundler@google.com>
>
> (sorry - patch attached instead of inline because, uhm, gmail white
> space mangles patches. Yes, we've complained about it).
>
> New text reads:
> + Allows SAS hosts to receive SAS Management Protocol (SMP)
> + frames. Selecting this option builds an SMP interpreter
> + into libsas. SMP frames are used to manage SAS expanders
> + and routing of SAS frames.
Actually, you're making it less clear.
What this option is doing is allowing the smp utilities to send SMP
frames to interrogate the HBA. Setting (or not setting) this option has
no effect on the SAS expanders. Essentially, it allows the HBA ports to
be treated the same as the expander ports from the point of view of a
software management tool.
> + For more details see:
> + http://www.scsita.org/aboutscsi/sas/tutorials.html
It's not the whole of this, just the Management upper layer.
> + http://www.t11.org/ftp/t11/pub/sm/hba/04-373v0.pdf
This latter one is the HBA API ... it's not really anything to do with
SMP.
James
next prev parent reply other threads:[~2008-08-12 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 21:35 [PATCH] 2.6.27-rc2 SCSI Rewrite help text for SCSI_SAS_HOST_SMP Grant Grundler
2008-08-12 21:46 ` James Bottomley [this message]
2008-08-12 22:34 ` Grant Grundler
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=1218577607.3549.57.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=grundler@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox