From: brantleycoile@me.com (Brantley Coile)
Subject: [TUHS] TUHS Digest, Vol 14, Issue 63
Date: Mon, 16 Jan 2017 18:45:52 -0500 [thread overview]
Message-ID: <E07A3D71-857A-44C9-80BB-BB8BE1B82373@me.com> (raw)
In-Reply-To: <C35441DB-7A62-498A-B173-3EA78FB89B15@tfeb.org>
Beware of SCSI folks who think they can design data network protocols.
Brantley
coraid.com
> On Jan 16, 2017, at 6:41 PM, Tim Bradshaw <tfb at tfeb.org> wrote:
>
> Less than ten years ago I wrote a big rant at people where I worked about fibre channel: all our machines had two entirely different networks attached to them: one built on ethernet which was at that point all Gb on new machines and 10Gb on some (I don't think that 10Gb switches were really available yet though) & where you could stuff a machine with interfaces for the cost of a good meal, and where everything just talked to everything else ... and one built on fibre channel which might have been 2Gb, where an interface cost as much as a car, and where interoperability involved weeks pissing around with firmware in the cards, and sometimes just buying new ones. Fibre channel was just laughably worse than ethernet.
>
> No one listened, of course, because my political skills are akin to those of a goat, and fibre channel is *storage* which is completely different than networking, somehow.
>
> Perhaps people still use fibre channel.
>
>> On 16 Jan 2017, at 16:44, Larry McVoy <lm at mcvoy.com> wrote:
>>
>> I held up the two cards, disclosed the cost, and said "this ATM card is
>> always going to be expensive but the ethernet card is gonna be $10 in
>> a year or two. Why? Volume. Every computer has ethernet, it's gonna
>> do nothing but get cheaper. And you're gonna see ethernet over fiber,
>> long haul, you're going to see 100 Mbit, gigabit ethernet, and it's
>> going to be cheap. ATM is going nowhere."
>
next prev parent reply other threads:[~2017-01-16 23:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 16:00 ` Doug McIlroy
2017-01-16 16:22 ` Marc Rochkind
2017-01-16 16:44 ` Larry McVoy
2017-01-16 16:52 ` Marc Rochkind
2017-01-16 19:17 ` Steve Johnson
2017-01-16 19:21 ` Larry McVoy
2017-01-16 19:57 ` Ken Thompson
2017-01-16 23:41 ` Tim Bradshaw
2017-01-16 23:45 ` Brantley Coile [this message]
2017-01-17 4:07 ` Jason Stevens
2017-01-17 5:22 ` William Corcoran
2017-01-17 11:43 ` Jason Stevens
2017-01-17 14:27 ` Joerg Schilling
2017-01-17 14:21 ` Joerg Schilling
2017-01-16 19:46 Noel Chiappa
2017-01-17 0:30 ` Brad Spencer
2017-01-17 15:32 Noel Chiappa
2017-01-18 14:29 ` Paul Ruizendaal
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=E07A3D71-857A-44C9-80BB-BB8BE1B82373@me.com \
--to=brantleycoile@me.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).