From: Jeremy Higdon <jeremy@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: jejb@steeleye.com, Eric.Moore@lsil.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/2] fusion SAS support
Date: Wed, 24 Aug 2005 00:08:40 -0700 [thread overview]
Message-ID: <20050824070840.GA568604@sgi.com> (raw)
In-Reply-To: <20050819162634.GA15401@lst.de>
On Fri, Aug 19, 2005 at 06:26:34PM +0200, Christoph Hellwig wrote:
> This patch implements minimal SAS support for fusion. It needs the
> previous set of fusion updates and the minimal SAS transport class to
> work. I'll probably revisit the transport class later to introduce a
> rport object, but I'll need some real enclosures with extenders and
> SMP ports to experiment with first. So my suggestion is to put the
> current state of the art into scsi-misc so it gets exposure in -mm
> and people can start reviwing the design and send patches. (Lots
> of thanks to James Smart btw, I had hoped to get more of this
> constructive critizism).
Hi Christoph,
I applied your four (sets of) patches, and they all seem to work
fine. When connected through an expander, the data is a little light,
but direct connect works great. Below, targets 0 and 1 are direct
connect to a 1064 chip, while targets 21-29 are through an expander.
pc-mdr5:/sys/class/sas_transport/target0:0:1 # lsscsi
[0:0:0:0] disk SEAGATE ST373454SS 0002 /dev/sda
[0:0:1:0] disk SEAGATE ST3146854SS 0002 /dev/sdb
[0:0:21:0] enclosu LSILOGIC SASX12 SEP v0.1 -
[0:0:22:0] disk SEAGATE ST373454SS 0002 /dev/sdk
[0:0:23:0] disk SEAGATE ST373454SS 0002 /dev/sdl
[0:0:24:0] disk SEAGATE ST3146854SS 0002 /dev/sdm
[0:0:25:0] disk SEAGATE ST3146854SS 0002 /dev/sdn
[0:0:26:0] disk SEAGATE ST3146854SS 0002 /dev/sdo
[0:0:27:0] disk SEAGATE ST3146854SS 0002 /dev/sdp
[0:0:28:0] disk SEAGATE ST373454SS 0002 /dev/sdq
[0:0:29:0] disk SEAGATE ST373454SS 0002 /dev/sdr
pc-mdr5:/sys/class/sas_transport/target0:0:1 # more /sys/class/sas_transport/target0\:0\:[01]/*
*** /sys/class/sas_transport/target0:0:0/device: directory ***
::::::::::::::
/sys/class/sas_transport/target0:0:0/device_type
::::::::::::::
end device
::::::::::::::
/sys/class/sas_transport/target0:0:0/initiator_port_protocols
::::::::::::::
none
::::::::::::::
/sys/class/sas_transport/target0:0:0/phy_identifier
::::::::::::::
1
::::::::::::::
/sys/class/sas_transport/target0:0:0/sas_address
::::::::::::::
0x5000c500004015fd
::::::::::::::
/sys/class/sas_transport/target0:0:0/target_port_protocols
::::::::::::::
ssp
*** /sys/class/sas_transport/target0:0:1/device: directory ***
::::::::::::::
/sys/class/sas_transport/target0:0:1/device_type
::::::::::::::
end device
::::::::::::::
/sys/class/sas_transport/target0:0:1/initiator_port_protocols
::::::::::::::
none
::::::::::::::
/sys/class/sas_transport/target0:0:1/phy_identifier
::::::::::::::
0
::::::::::::::
/sys/class/sas_transport/target0:0:1/sas_address
::::::::::::::
0x5000c50000000ef5
::::::::::::::
/sys/class/sas_transport/target0:0:1/target_port_protocols
::::::::::::::
ssp
*** /sys/class/sas_transport/target0:0:24/device: directory ***
::::::::::::::
/sys/class/sas_transport/target0:0:24/device_type
::::::::::::::
none
::::::::::::::
/sys/class/sas_transport/target0:0:24/initiator_port_protocols
::::::::::::::
none
::::::::::::::
/sys/class/sas_transport/target0:0:24/phy_identifier
::::::::::::::
0
::::::::::::::
/sys/class/sas_transport/target0:0:24/sas_address
::::::::::::::
0x0
::::::::::::::
/sys/class/sas_transport/target0:0:24/target_port_protocols
::::::::::::::
none
next prev parent reply other threads:[~2005-08-24 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 16:26 [PATCH 0/2] fusion SAS support Christoph Hellwig
2005-08-24 7:08 ` Jeremy Higdon [this message]
2005-08-24 8:57 ` Christoph Hellwig
2005-08-24 9:10 ` Jeremy Higdon
2005-08-24 9:14 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 23:15 Moore, Eric Dean
2005-08-29 8:01 ` Christoph Hellwig
2005-08-29 18:55 Moore, Eric Dean
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=20050824070840.GA568604@sgi.com \
--to=jeremy@sgi.com \
--cc=Eric.Moore@lsil.com \
--cc=hch@lst.de \
--cc=jejb@steeleye.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.