From: Jeff Garzik <jgarzik@pobox.com>
To: ralph+d@istop.com
Cc: Dan Hollis <goemon@anime.net>, linux-netdev <netdev@oss.sgi.com>
Subject: Re: [Bonding-devel] Re: [RFC][bonding] Improve VLAN support on top of bonding
Date: Tue, 15 Jul 2003 18:30:22 -0400 [thread overview]
Message-ID: <3F14807E.30402@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.51.0307151434100.4590@ns.istop.com>
Ralph Doncaster wrote:
> On Tue, 15 Jul 2003, Dan Hollis wrote:
>
>
>>That is exactly what it does. hw tcp checksumming helps a LOT at gbe rates
>
>
> This still doesn't make any sense. The copy from user-space to kernel
> space does the checksum as far as I recall (unless you use the
> router-not-host kernel build option).
Not for the zero-copy case.
Jeff
next prev parent reply other threads:[~2003-07-15 22:30 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
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 [this message]
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=3F14807E.30402@pobox.com \
--to=jgarzik@pobox.com \
--cc=goemon@anime.net \
--cc=netdev@oss.sgi.com \
--cc=ralph+d@istop.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).