From: Francois Romieu <romieu@fr.zoreil.com>
To: Jeff Sipek <jeffpc@optonline.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
Dave Jones <davej@codemonkey.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
netdev@oss.sgi.com
Subject: Re: [PATCH - RFC] [1/5] 64-bit network statistics - generic net
Date: Sat, 5 Jul 2003 23:51:31 +0200 [thread overview]
Message-ID: <20030705235131.A10511@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200307051700.32533.jeffpc@optonline.net>; from jeffpc@optonline.net on Sat, Jul 05, 2003 at 04:59:05PM -0400
Jeff Sipek <jeffpc@optonline.net> :
[network counter overflow on 32 bits systems]
> The thing is that x86 is here to stay for quite some time. Even if 64-bit
> processors take over the market, you will have so many "old" computers that
> can:
>
> - - be thrown out
> - - donated to some institution
> - - converted to routers, and other "embedded" systems
>
> Plus, they will be dirt cheap.
- the PCI bus don't/won't/can't handle multiple 10 Gb/s adapters;
- nobody sane would recycle x86 systems as core routers after having bought
a few Gb/s link.
--
Ueimor
next prev parent reply other threads:[~2003-07-05 21:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 2:31 Jeff Sipek
2003-07-04 2:46 ` Jeff Garzik
2003-07-04 6:02 ` Jeff Sipek
2003-07-04 3:08 ` Linus Torvalds
2003-07-04 5:27 ` Jeff Sipek
2003-07-04 7:05 ` bert hubert
2003-07-05 18:49 ` Jeff Sipek
2003-07-05 21:46 ` Ben Greear
2003-07-04 9:47 ` Jan-Benedict Glaw
2003-07-04 17:57 ` Jeff Sipek
2003-07-05 19:58 ` Bernd Eckenfels
2003-07-05 20:37 ` Jeff Sipek
2003-07-05 20:40 ` Jeff Garzik
2003-07-05 20:59 ` Jeff Sipek
2003-07-05 21:51 ` Francois Romieu [this message]
2003-07-05 22:39 ` Jeff Sipek
2003-07-05 23:44 ` Francois Romieu
2003-07-05 22:54 ` Roland Dreier
2003-07-05 21:41 ` Ben Greear
2003-07-06 7:27 ` Alan Cox
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=20030705235131.A10511@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=ecki@calista.eckenfels.6bone.ka-ip.net \
--cc=jeffpc@optonline.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®