From: Ben Greear <greearb@candelatech.com>
To: Dan Hollis <goemon@anime.net>
Cc: Shmulik Hen <shmulik.hen@intel.com>,
bond-devel <bonding-devel@lists.sourceforge.net>,
linux-net <linux-net@vger.kernel.org>,
linux-netdev <netdev@oss.sgi.com>,
"David S. Miller" <davem@redhat.com>,
Jeff Garzik <jgarzik@pobox.com>, Jay Vosburgh <fubar@us.ibm.com>,
Amir Noam <amir.noam@intel.com>,
Noam Marom <noam.marom@intel.com>,
Tsippy Mendelson <tsippy.mendelson@intel.com>
Subject: Re: [Bonding-devel] Re: [RFC][bonding] Improve VLAN support on top of bonding
Date: Tue, 15 Jul 2003 11:13:58 -0700 [thread overview]
Message-ID: <3F144466.8010003@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307151054350.5112-100000@sasami.anime.net>
Dan Hollis wrote:
> On Tue, 15 Jul 2003, Ben Greear wrote:
>
>>I'd consider ignoring the HW accel unless you can prove it actually helps
>>performance to a noticeable degree. I have never seen results of any benchmarking
>>related to this...
>
>
> For gigabit ethernet, it makes a *H*U*G*E* difference.
I'm curious to see numbers. The VLAN shim is only inserting
a small shim header, at at most shifting the first part of the packet
when sent a pre-built packet.
Maybe the hw-accel turns on tcp checksumming or something too??
>
> -Dan
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2003-07-15 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 13:55 [RFC][bonding] Improve VLAN support on top of bonding Shmulik Hen
2003-07-15 17:24 ` Ben Greear
2003-07-15 17:55 ` [Bonding-devel] " Dan Hollis
2003-07-15 18:13 ` Ben Greear [this message]
2003-07-15 18:16 ` Dan Hollis
2003-07-15 18:36 ` Ralph Doncaster
2003-07-15 19:20 ` Dan Hollis
2003-07-15 22:30 ` Jeff Garzik
2003-07-16 12:33 ` Ralph Doncaster
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=3F144466.8010003@candelatech.com \
--to=greearb@candelatech.com \
--cc=amir.noam@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=davem@redhat.com \
--cc=fubar@us.ibm.com \
--cc=goemon@anime.net \
--cc=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=noam.marom@intel.com \
--cc=shmulik.hen@intel.com \
--cc=tsippy.mendelson@intel.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).