netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Jan Ceuleers <jan.ceuleers@computer.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: Default offload settings in Ethernet drivers
Date: Thu, 11 Dec 2008 19:52:48 +0000	[thread overview]
Message-ID: <1229025168.3006.41.camel@achroite> (raw)
In-Reply-To: <49416A4B.7060205@computer.org>

On Thu, 2008-12-11 at 20:30 +0100, Jan Ceuleers wrote:
> Stephen Hemminger wrote:
> > I don't think there will be any difference. Linux (mainline) doesn't
> > do TOE. It does do segmentation offload, and any driver that can
> > do segmentation offload enables it by default.
> 
> Stephen,
> 
> Thanks for your reply. My experience with the r8169 driver is that it 
> does support rx checksumming, tx checksumming, scatter/gather and tcp 
> segmentation, but out of the above only enables rx checksumming by default.
> 
> The other two ethernet drivers I have hardware for don't support any 
> hardware-assisted offloads (that is: they all support generic 
> segmentation offload but that isn't hardware-assisted and it is also not 
> enabled by default).

Since v2.6.27, GSO is enabled by default for devices that can do TX
scatter/gather and checksum offload.

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.


      reply	other threads:[~2008-12-11 19:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 18:41 Default offload settings in Ethernet drivers Jan Ceuleers
2008-12-11 18:54 ` Stephen Hemminger
2008-12-11 19:10   ` Rick Jones
2008-12-11 19:29   ` Ben Hutchings
2008-12-11 19:30   ` Jan Ceuleers
2008-12-11 19:52     ` 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=1229025168.3006.41.camel@achroite \
    --to=bhutchings@solarflare.com \
    --cc=jan.ceuleers@computer.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).