From: Ben Hutchings <bhutchings@solarflare.com>
To: "Dan Noé" <dnoe@limebrokerage.com>
Cc: netdev@vger.kernel.org
Subject: Re: TCP stateless offload with bonding?
Date: Fri, 5 Sep 2008 17:38:29 +0100 [thread overview]
Message-ID: <20080905163828.GK7908@solarflare.com> (raw)
In-Reply-To: <48C15885.9050908@limebrokerage.com>
Dan Noé wrote:
> The Documentation/networking/bonding.txt file talks about VLAN offload
> support and the bonding driver, but not TCP segmentation, UDP/TCP
> checksum, etc, offloading. Is this supported by the bonding driver, and
> if so, how is it configured?
>
> If it matters, we are using bonding for HA/failover, not for bandwidth
> aggregation.
The bonding driver generally provides all the offload features that all its
slave devices provide. You can configure this by using ethtool on the slave
devices.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2008-09-05 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 16:04 TCP stateless offload with bonding? Dan Noé
2008-09-05 16:38 ` Ben Hutchings [this message]
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=20080905163828.GK7908@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=dnoe@limebrokerage.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).