From: "David S. Miller" <davem@redhat.com>
To: Larry McVoy <lm@bitmover.com>
Cc: piggin@cyberone.com.au, icerbofh@hotmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: Fire Engine??
Date: Tue, 25 Nov 2003 18:48:25 -0800 [thread overview]
Message-ID: <20031125184825.648aae7c.davem@redhat.com> (raw)
In-Reply-To: <20031126021111.GA10193@work.bitmover.com>
On Tue, 25 Nov 2003 18:11:11 -0800
Larry McVoy <lm@bitmover.com> wrote:
> I used to think otherwise, while I was a Sun employee, and Sun employee #1
> pointed out to me that CPUs and memory were getting faster more quickly than
> the TOE type answers could come to market. He was right then and he seems
> to still be right.
Maybe this was at least partially the impetus behind his recent
departure from the company. And if not the impetus, a possible straw
that broke the camel's back.
How fast will cpus be when Sun actually deploys this stuff?
A commodity x86 U1 box at that time will probably have 6+ GHZ
cpus in it, and super-duper-DDR or whatever the current memory
technology will be. Why do I need Sun's TOE crap in this box?
Where's all that precious CPU I need to be saving?
This stuff isn't really useful for huge database servers either.
Where do they plan to do, put Solaris10 on iSCSI drives? ROFL! :)
These days Sun is already several laps behind before the green flag
even comes out to start the race.
next prev parent reply other threads:[~2003-11-26 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 0:15 Fire Engine?? Mr. BOFH
2003-11-26 1:48 ` [OT] " Nick Piggin
2003-11-26 2:11 ` Larry McVoy
2003-11-26 2:48 ` David S. Miller [this message]
2003-11-26 3:31 ` Rik van Riel
2003-11-26 2:30 ` David S. Miller
2003-11-26 5:41 ` Valdis.Kletnieks
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=20031125184825.648aae7c.davem@redhat.com \
--to=davem@redhat.com \
--cc=icerbofh@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=piggin@cyberone.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.