netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org, "Kok,
	 Auke-jan H" <auke-jan.h.kok@intel.com>,
	jeff@garzik.org
Subject: Re: [PATCH 3/5] e1000e: Allow TSO to trickle down to VLAN device
Date: Wed, 30 Apr 2008 08:54:37 +0200	[thread overview]
Message-ID: <481817AD.1010306@trash.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC32904FE0E6B@orsmsx414.amr.corp.intel.com>

Waskiewicz Jr, Peter P wrote:
>> In any case I would prefer to avoid having drivers mess with VLAN
>> device flags. How about adding a device flag indicating that the
>> driver supports TSO + VLAN acceleration and using the
>> NETDEV_FEAT_CHANGE notification inside the VLAN code do adjust
>> the device's flags properly?
> 
> I've been looking into this, and I agree this makes sense when creating
> a new VLAN to get the device flags to the VLAN device.  However, we need
> to get the TSO and/or Tx checksum offload feature flags off all VLAN
> devices when the parent device has it turned off.  I don't see any clean
> way of doing this with netdev_features_change().  I'd really love to
> implement this correctly, so if you have any ideas on how to handle this
> latter case, I'm all ears.  :-)


Whats the problem with doing:

- on VLAN creation: copy VLAN flag from lower device if lowerdev
   has NETIF_F_<flag indicating non-broken TSO+VLAN accel>

- on change of TSO/checksumming flags of lower device:
   use netdevice notifier to adjust the settings for all
   VLANs on that device

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-04-30  6:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 17:05 [PATCH 1/5] e1000e: cleanup several stats issues Auke Kok
2008-04-14 17:06 ` [PATCH 2/5] e1000e: Add interrupt moderation run-time ethtool interface Auke Kok
2008-04-14 19:24   ` Andi Kleen
2008-04-14 19:31     ` Rick Jones
2008-04-14 19:35     ` Jeff Garzik
2008-04-14 19:53       ` Andi Kleen
2008-04-14 20:09       ` Kok, Auke
2008-04-14 17:06 ` [PATCH 3/5] e1000e: Allow TSO to trickle down to VLAN device Auke Kok
2008-04-14 17:11   ` Patrick McHardy
2008-04-17 21:45     ` Kok, Auke
2008-04-21 14:24       ` Patrick McHardy
2008-04-22  7:46         ` Waskiewicz Jr, Peter P
2008-04-30  0:42         ` Waskiewicz Jr, Peter P
2008-04-30  6:54           ` Patrick McHardy [this message]
2008-04-30  6:56             ` Patrick McHardy
2008-04-14 17:06 ` [PATCH 4/5] e1000e: Fix HW Error on es2lan, ARP capture issue by BMC Auke Kok
2008-04-14 17:06 ` [PATCH 5/5] e1000e: lower ring minimum size to 64 Auke Kok

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=481817AD.1010306@trash.net \
    --to=kaber@trash.net \
    --cc=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@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).