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: Ben Hutchings <bhutchings@solarflare.com>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [RFC, VLAN]: Propagate selected feature bits to VLAN devices
Date: Wed, 21 May 2008 01:59:07 +0200	[thread overview]
Message-ID: <483365CB.8010100@trash.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC329051AC9FE@orsmsx414.amr.corp.intel.com>

Waskiewicz Jr, Peter P wrote:
>>> Shouldn't this mask the flags out of vlandev->features first?
>>>   
>> Yes, thanks.
>>>> +	dev->features = real_dev->features & (NETIF_F_TSO | 
>> NETIF_F_TSO6);
>>>>     
>>> This should also test the NETIF_F_VLAN_TSO flag and should copy the 
>>> NETIF_F_ALL_CSUM and NETIF_F_SG flags since TSO requires those (see
>>> register_netdevice() feature fix-up).  Peter pointed out that TX 
>>> checksum offload for VLANs might be available even without TSO; the 
>>> same goes for scatter-gather but I don't know whether it's 
>> worth adding a flag for that.
>>>   
>> Thanks, I added NETIF_F_SG to the VLAN TSO flags and added a 
>> NETIF_F_VLAN_CSUM flag for TX checksums. I didn't change 
>> GSO_SHIFT so far.
> 
> I've tested your latest patch with an in-house modified ixgbe driver,
> both with CSUM and TSO.  This patch works great for adding and removing
> the feature flags on demand.  Thanks for putting this together Patrick.
> 
> -PJ Waskiewicz
> <peter.p.waskiewicz.jr@intel.com>

Great, I didn't notice your email before I saw Dave already
applied it :) Thanks Peter.


  reply	other threads:[~2008-05-20 23:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 14:37 [RFC, VLAN]: Propagate selected feature bits to VLAN devices Patrick McHardy
2008-05-20 14:38 ` Patrick McHardy
2008-05-20 14:48 ` Ben Hutchings
2008-05-20 14:51   ` Patrick McHardy
2008-05-20 15:46     ` Ben Greear
2008-05-20 16:20       ` Ben Hutchings
2008-05-20 16:27         ` Patrick McHardy
2008-05-20 16:28         ` Ben Greear
2008-05-20 17:22           ` Waskiewicz Jr, Peter P
2008-05-20 17:23             ` Patrick McHardy
2008-05-20 18:05 ` Ben Hutchings
2008-05-20 18:31   ` Patrick McHardy
2008-05-20 19:58     ` Waskiewicz Jr, Peter P
2008-05-20 23:59       ` Patrick McHardy [this message]
2008-05-20 21:55     ` David Miller
2008-05-20 23:58       ` Patrick McHardy
2008-05-21 15:49 ` Herbert Xu
2008-05-21 16:28   ` Patrick McHardy
2008-05-21 23:39     ` Herbert Xu
2008-05-22 17:47       ` Waskiewicz Jr, Peter P
2008-05-22 18:03         ` Patrick McHardy
2008-05-22 18:18           ` Waskiewicz Jr, Peter P
2008-05-22 18:25             ` Patrick McHardy
2008-05-22 18:57               ` Waskiewicz Jr, Peter P

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=483365CB.8010100@trash.net \
    --to=kaber@trash.net \
    --cc=bhutchings@solarflare.com \
    --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).