From: Vojtech Pavlik <vojtech@suse.cz>
To: Justin Piszcz <war@starband.net>, Mike Ricketts <mike@earth.li>,
janvapan <jvp@wanadoo.es>,
linux-kernel@vger.kernel.org
Subject: Re: Recommendations about a 100/10 NIC
Date: Mon, 4 Mar 2002 10:54:58 +0100 [thread overview]
Message-ID: <20020304105458.A3582@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10203031559090.801-100000@oakley.chf> <3C824E68.13EE719@starband.net> <20020304051510.GG353@matchmail.com>
In-Reply-To: <20020304051510.GG353@matchmail.com>; from mfedyk@matchmail.com on Sun, Mar 03, 2002 at 09:15:10PM -0800
On Sun, Mar 03, 2002 at 09:15:10PM -0800, Mike Fedyk wrote:
> On Sun, Mar 03, 2002 at 11:25:12AM -0500, Justin Piszcz wrote:
> > Full Duplex hub = Better
>
> = switch ! hub
Well, most of those have just one packet sized buffer, so they are hubs
performancewise, while they're switches by technology ...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-03-04 9:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10203031559090.801-100000@oakley.chf>
2002-03-03 16:25 ` Recommendations about a 100/10 NIC Justin Piszcz
2002-03-04 5:15 ` Mike Fedyk
2002-03-04 9:54 ` Vojtech Pavlik [this message]
[not found] <fa.fifmv4v.ogc1qa@ifi.uio.no>
[not found] ` <fa.jgnh1iv.1ek48ih@ifi.uio.no>
2002-03-04 6:49 ` Dan Maas
2002-03-03 12:18 janvapan
2002-03-03 14:22 ` Justin Piszcz
2002-03-03 20:29 ` Bernd Eckenfels
2002-03-03 21:04 ` Hans-Christian Armingeon
2002-03-04 3:05 ` rddunlap
2002-03-03 21:37 ` Hans-Christian Armingeon
2002-03-03 17:15 ` J Sloan
2002-03-03 20:39 ` LA Walsh @ tlinx.org
2002-03-04 1:04 ` J Sloan
2002-03-07 8:21 ` Kelsey Hudson
2002-03-06 17:15 ` Ken Brownfield
2002-03-06 17:36 ` John Jasen
2002-03-06 17:28 ` Tim Hockin
2002-03-06 18:30 ` Michael Sterrett -Mr. Bones.-
2002-03-06 18:33 ` John Jasen
2002-03-06 21:42 ` Francois Romieu
2002-03-08 1:47 ` Ken Brownfield
2002-03-07 5:06 ` J Sloan
2002-03-07 8:16 ` Kelsey Hudson
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=20020304105458.A3582@ucw.cz \
--to=vojtech@suse.cz \
--cc=jvp@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@earth.li \
--cc=war@starband.net \
/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.