From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Eric.Moore@lsil.com
Subject: Re: Serial Attached SCSI Driver Interface (SDI)
Date: Mon, 15 Nov 2004 13:29:13 -0500 [thread overview]
Message-ID: <4198F579.9080606@adaptec.com> (raw)
In-Reply-To: <4198EF00.2010305@pobox.com>
Jeff Garzik wrote:
> ug.
>
> These ioctl mechanisms almost always (a) have design flaws [which cannot
> be corrected, since they are in a spec] and (b) duplicate other
> functionality of the Linux kernel. The SNIA ioctl mess is a great
> example of this.
>
> Without any additional info, my first reaction is that this is yet more
> stuff Linux doesn't need.
I don't want to speculate on whether it will or not be an ioctl
mechanism. But most importantly, by architecture design, SAS
really _needs_ a control management infrastructure of its components
and _maybe_ a representation somewhere in the OS. Since it really
represents a "storage network" and in certain instances a complicated
one at that.
That control management infrastructure would be shared by (used by
both) the OS and the kernel (for the appropriate functionaly needed/provided).
I've just got official word that SDI would be "the industry
standard version of CSMI".
It's a good thing,
Luben
next prev parent reply other threads:[~2004-11-15 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 17:48 Serial Attached SCSI Driver Interface (SDI) Salyzyn, Mark
2004-11-15 18:01 ` Jeff Garzik
2004-11-15 18:29 ` Luben Tuikov [this message]
2004-11-15 18:49 ` Jeff Garzik
2004-11-15 20:00 ` Luben Tuikov
2004-11-15 20:41 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 18:14 Salyzyn, Mark
2004-11-15 22:47 ` Jeff Garzik
2004-11-15 17:40 Moore, Eric Dean
2004-11-15 17:22 Luben Tuikov
2004-11-15 17:40 ` 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=4198F579.9080606@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=Eric.Moore@lsil.com \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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).