From: Bernd Eckenfels <usenet2001-12@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Two hdds on one channel - why so slow?
Date: Fri, 4 Jan 2002 19:40:00 +0100 [thread overview]
Message-ID: <E16MZG4-0001ch-00@sites.inka.de> (raw)
In-Reply-To: <200201041725.g04HPwSr031984@svr3.applink.net>
In article <200201041725.g04HPwSr031984@svr3.applink.net> you wrote:
> Why go Fibre Channel when Firewire is really starting to catch on?
Because Firewire is Consumer electronics and nearly dead. Dont now of
Enterpise Solutions with Firewire. Besides there is no switching support for
it.
I am happy to see those FC-S/ATA Controlers soon :)
Greetings
Bernd
next prev parent reply other threads:[~2002-01-04 18:40 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 14:02 Two hdds on one channel - why so slow? Jesse Pollard
2002-01-04 16:33 ` Bernd Eckenfels
[not found] ` <Pine.LNX.4.43.0201041154010.14678-100000@filesrv1.baby-dragons.com>
2002-01-04 17:14 ` Bernd Eckenfels
2002-01-04 17:22 ` Timothy Covell
2002-01-04 18:40 ` Bernd Eckenfels [this message]
2002-01-04 19:32 ` Jeffrey W. Baker
2002-01-05 12:02 ` Henning P. Schmiedehausen
2002-01-04 20:29 ` Timothy Covell
2002-01-08 23:49 ` Ricky Beam
2002-01-09 0:50 ` Timothy Covell
2002-01-09 1:22 ` Ricky Beam
2002-01-04 17:40 ` Jesse Pollard
2002-01-08 12:41 ` Rob Landley
2002-01-08 21:18 ` William Park
2002-01-09 10:56 ` Rob Landley
2002-01-09 19:50 ` William Park
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 17:06 Jesse Pollard
2002-01-07 17:17 ` Tommy Reynolds
2002-01-04 19:29 Dana Lacoste
2002-01-05 11:58 ` Henning P. Schmiedehausen
2002-01-05 12:20 ` Petro
2002-01-09 0:04 ` Ricky Beam
[not found] <Pine.LNX.4.33.0201040844130.14385-100000@coffee.psychology.mcmaster.ca>
2002-01-04 17:18 ` Krzysztof Oledzki
[not found] <Pine.LNX.4.33.0201021452120.8693-100000@coffee.psychology.mcmaster.ca>
2002-01-04 9:28 ` Krzysztof Oledzki
2002-01-03 15:49 Dana Lacoste
2002-01-03 16:44 ` Mark Hahn
2002-01-01 22:34 Krzysztof Oledzki
2002-01-01 23:07 ` Brian
2002-01-01 23:32 ` Andre Hedrick
2002-01-02 0:52 ` H. Peter Anvin
2002-01-02 1:19 ` Benjamin LaHaise
2002-01-02 1:24 ` H. Peter Anvin
2002-01-02 2:03 ` Benjamin LaHaise
2002-01-02 4:13 ` Andre Hedrick
2002-01-02 17:21 ` Krzysztof Oledzki
2002-01-02 18:41 ` Vojtech Pavlik
2002-01-02 19:31 ` Andre Hedrick
2002-01-02 20:23 ` Brian
2002-01-02 23:30 ` Ricky Beam
2002-01-03 1:52 ` Mark Hahn
2002-01-03 5:57 ` Ricky Beam
2002-01-04 2:54 ` Petro
2002-01-04 3:04 ` Arnaldo Carvalho de Melo
2002-01-04 18:19 ` Stephan von Krawczynski
2002-01-04 18:38 ` Alan Cox
2002-01-04 18:30 ` Stephan von Krawczynski
2002-01-05 0:52 ` J.A. Magallon
2002-01-05 9:41 ` Nick Holloway
2002-01-05 12:04 ` Henning P. Schmiedehausen
2002-01-05 1:28 ` Andre Hedrick
2002-01-08 23:59 ` Ricky Beam
2002-01-09 0:10 ` Mark Hahn
2002-01-09 15:27 ` Andre Hedrick
2002-01-08 23:46 ` Ricky Beam
2002-01-07 8:11 ` Stevie O
2002-01-07 15:57 ` Thomas Molina
2002-01-07 16:14 ` Ricky Beam
2002-01-07 16:40 ` Thomas Molina
2002-01-07 18:48 ` Andre Hedrick
2002-01-07 20:19 ` Petro
2002-01-07 22:31 ` Dmitri Pogosyan
2002-01-08 13:50 ` Alan Cox
2002-01-08 14:45 ` Mike Dresser
2002-01-08 14:57 ` James A Sutherland
2002-01-08 17:15 ` Wakko Warner
2002-01-02 21:23 ` Jeffrey W. Baker
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=E16MZG4-0001ch-00@sites.inka.de \
--to=usenet2001-12@lina.inka.de \
--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