From: Mike Fedyk <mfedyk@matchmail.com>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata in 2.4.24?
Date: Tue, 2 Dec 2003 15:40:51 -0800 [thread overview]
Message-ID: <20031202234051.GE4154@mis-mike-wstn.matchmail.com> (raw)
In-Reply-To: <bqj6k0$e2p$1@gatekeeper.tmr.com>
On Tue, Dec 02, 2003 at 11:18:24PM +0000, Bill Davidsen wrote:
> In article <20031202230216.GB4154@mis-mike-wstn.matchmail.com>,
> Mike Fedyk <mfedyk@matchmail.com> wrote:
> | On Tue, Dec 02, 2003 at 10:34:20PM +0000, Bill Davidsen wrote:
> | > after each O_SYNC write, so that's probably not practical. Clearly the
> | > best solution is a full SCSI implementation over PATA/SATA, but that
> | > would eliminate some of the justification for SCSI devices at premium
> | > prices.
> |
> | In many ways, that is exactly what SATA is. :)
>
> Until multiple devices be string are available SATA will have logistical
> problems scaling. The small cable is an advantage running a few drives
> in a box, but a server with 40 drives or so would go from a cable bundle
> out the back, about 5cm by 1 cm, to a real bunch of those little round
> cables running everywhere. Certainly doable, but I think I'd name the
> server "Medusa" if I built it.
>
Isn't this what SSCSI (Serial SCSI) will be doing also -- one drive one cable?
I'd imagine that you'd have one connection to the enclosure, and the entire
enclosure will look like a single drive. I've heard of SCSI enclosures like
this (even ones that hold ide drives, but talk scsi to the host).
> I believe SATA-2 will address this, if I may believe what's projected
> for an unwritten standard.
There will probably be many ways to get around any issues that may come up
with SATA until SATA-2 comes out.
next prev parent reply other threads:[~2003-12-02 23:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 18:27 linux-2.4.23 released Marcelo Tosatti
2003-11-28 19:06 ` Willy Tarreau
2003-11-28 22:55 ` J.A. Magallon
2003-11-29 22:26 ` libata in 2.4.24? Samuel Flory
2003-11-29 23:10 ` Marcelo Tosatti
2003-12-01 10:43 ` Marcelo Tosatti
2003-12-01 18:06 ` Samuel Flory
2003-12-01 21:12 ` Greg Stark
2003-12-01 21:23 ` Samuel Flory
2003-12-01 21:44 ` Greg Stark
2003-12-01 22:00 ` Jeff Garzik
2003-12-01 22:06 ` Samuel Flory
2003-12-01 22:00 ` Erik Steffl
2003-12-02 5:36 ` Greg Stark
[not found] ` <20031202055336.GO1566@mis-mike-wstn.matchmail.com>
2003-12-02 5:58 ` Mike Fedyk
2003-12-02 16:31 ` Greg Stark
2003-12-02 17:40 ` Mike Fedyk
2003-12-02 18:04 ` Jeff Garzik
2003-12-02 18:46 ` Mike Fedyk
2003-12-02 18:49 ` Jeff Garzik
2003-12-04 8:18 ` Jens Axboe
2003-12-02 18:02 ` Jeff Garzik
2003-12-02 18:51 ` Greg Stark
2003-12-02 19:06 ` Jeff Garzik
2003-12-02 20:10 ` Greg Stark
2003-12-02 20:16 ` Jeff Garzik
2003-12-02 20:34 ` Greg Stark
2003-12-02 22:34 ` bill davidsen
2003-12-02 23:02 ` Mike Fedyk
2003-12-02 23:18 ` bill davidsen
2003-12-02 23:40 ` Mike Fedyk [this message]
2003-12-03 0:01 ` Jeff Garzik
2003-12-03 0:47 ` Jamie Lokier
2003-12-07 5:33 ` Bill Davidsen
2003-12-01 21:36 ` Justin Cormack
2003-12-01 13:41 Xose Vazquez Perez
2003-12-01 14:11 ` Marcelo Tosatti
2003-12-02 19:59 ` Stephan von Krawczynski
2003-12-02 22:05 ` bill davidsen
2003-12-02 22:34 ` Jeff Garzik
2003-12-03 0:34 Xose Vazquez Perez
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=20031202234051.GE4154@mis-mike-wstn.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).