Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH] ixgbe/ixgbevf: Enables TSO for MPLS encapsulated packets
Date: Thu, 17 Nov 2016 21:53:30 -0800	[thread overview]
Message-ID: <1479448410.2420.92.camel@intel.com> (raw)
In-Reply-To: <1479236637.26945.70.camel@intel.com>

On Tue, 2016-11-15 at 19:03 +0000, Peterson, Scott D wrote:
> This patch advertises TSO & GSO features in netdev->mpls_features.?
> In ixgbe(vf)_tso() where we set up segmentation offload, the IP?
> header will be the inner network header when eth_p_mpls() indicates
> the Ethernet protocol is MPLS (UC or MC).
> 
> We're submitting this upstream first, because it depends on related
> upstream changes not yet present in the OOT drivers.
> 
> Suggested-by: Alexander Duyck <alexander.h.duyck@intel.com>
> Signed-off-by: Scott Peterson <scott.d.peterson@intel.com>
> ---
> 
> ?drivers/net/ethernet/intel/ixgbe/ixgbe_main.c?????| 12 ++++++++++--
> ?drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 12 ++++++++++--
> ?2 files changed, 20 insertions(+), 4 deletions(-)

Not sure what is going on, but your patch does not apply. ?I tried
downloading your patch from patchworks and it says the patch is corrupt.

I will look at this later tonight to see if your patch can be applied by
hand for testing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20161117/83a698f6/attachment.asc>

      parent reply	other threads:[~2016-11-18  5:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 19:03 [Intel-wired-lan] [net-next PATCH] ixgbe/ixgbevf: Enables TSO for MPLS encapsulated packets Peterson, Scott D
2016-11-15 22:27 ` Peterson, Scott D
2016-11-18  5:53 ` Jeff Kirsher [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=1479448410.2420.92.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=intel-wired-lan@osuosl.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