From: "Robert Tarte" <robt@PacificCodeWorks.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: RE: [PATCH] aic94xx: fix routing algorithms
Date: Tue, 11 Jul 2006 08:49:18 -0700 [thread overview]
Message-ID: <16C8363E16D7234AB844FDB52D4AEA650C2DBB@ntserv.PacificCodeWorks.local> (raw)
> No ... this is the programme in annex L of sas-2, isn't it? Even if
it
> were available somewhere, the aic94xx doesn't yet have the necessary
SMP
> tap to try it.
[Tarte, Robert] I wrote an expander simulator that I ran in user space
for the adp94xx. I extracted the routing code from the adp94xx driver
and ran through numerous configurations hand checking the table to make
sure that it came up with the right answer.
next reply other threads:[~2006-07-11 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 15:49 Robert Tarte [this message]
2006-07-11 16:18 ` [PATCH] aic94xx: fix routing algorithms James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 8:30 Robert Tarte
2006-07-11 12:54 ` James Bottomley
2006-07-09 20:41 James Bottomley
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=16C8363E16D7234AB844FDB52D4AEA650C2DBB@ntserv.PacificCodeWorks.local \
--to=robt@pacificcodeworks.com \
--cc=James.Bottomley@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox