From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] plan9 on vmware esx
Date: Fri, 2 Oct 2009 01:15:20 -0400 [thread overview]
Message-ID: <acd9b0f22b07c6cc5a4adb3a5facec99@ladd.quanstro.net> (raw)
In-Reply-To: <<18364.1254459813@lunacy.ugrad.cs.cmu.edu>>
> Run in fear.
>
> Despite having a number which is just a wee bit higher than the
> things supported by the existing Plan 9 NCR/LSI SCSI driver,
> this is an utterly different beast, based on LSI's "Fusion"
> architecture, which in theory simplifies things vastly for the
> host over the old sequencer/script architecture, but all of the
> simplification is balanced out by vast complexity additions in
> other areas (addressing devices in terms of target and LUN is
> obsolete, so there are two or three other ways that devices can
> identify themselves, and a host is supposed to set up a mapping
> from long identifiers to short ones for, and for some reason I
> didn't get on first reading the host is supposed to use the same
> mapping across reboots).
regardless of what one things of the fusion architecture,
most of these complications are direct results about how
modern scsi works; any modern scsi driver will have the
same issues. the address of a scsi device will have depends
on the protocol used for disk access. sas for example
uses "sas addresses" aka a wwn. if you avoid dealing with
expanders, sas simplifies quite a bit. sdorion (contrib
quanstro/sd) is a "combined mode" driver. combined mode
means that it is able to talk to either sata or sas hardware.
- erik
next parent reply other threads:[~2009-10-02 5:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<18364.1254459813@lunacy.ugrad.cs.cmu.edu>
2009-10-02 5:15 ` erik quanstrom [this message]
2009-10-02 13:45 ` Dave Eckhardt
2009-10-02 13:57 ` Devon H. O'Dell
2009-10-02 16:35 ` Skip Tavakkolian
2009-10-05 5:25 ` YAMANASHI Takeshi
2009-10-05 19:53 ` lucio
[not found] <<4ff6efe6c7ea3550ae2823dad8319d55@9netics.com>
2009-10-05 13:33 ` erik quanstrom
[not found] <<bf64731d0910042225p48cde43dkbc50fef20e2a59c8@mail.gmail.com>
2009-10-05 5:30 ` erik quanstrom
2009-10-05 6:04 ` ron minnich
2009-10-05 6:38 ` Skip Tavakkolian
2009-10-05 8:19 ` YAMANASHI Takeshi
2009-10-05 19:55 ` lucio
[not found] <<20954.1254491102@lunacy.ugrad.cs.cmu.edu>
2009-10-02 16:47 ` erik quanstrom
2009-10-01 23:30 Skip Tavakkolian
2009-10-02 3:54 ` 6o205zd02
2009-10-02 8:08 ` YAMANASHI Takeshi
2009-10-02 16:15 ` Skip Tavakkolian
2009-10-02 5:03 ` Dave Eckhardt
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=acd9b0f22b07c6cc5a4adb3a5facec99@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).