Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <aduyck@mirantis.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH 0/3] ixgbe/i40e: Fix ATR functionality related to raw sockets and IPv6 extension headers
Date: Mon, 25 Jan 2016 19:31:17 -0800	[thread overview]
Message-ID: <20160126032616.16387.86351.stgit@localhost.localdomain> (raw)

This patch set addresses several things.

First the i40e driver was lacking extension header parsing for ATR so I
went ahead and added support via the ipv6_find_hdr call.

Second the vxlan_port code in ixgbe was a bit convoluted and needed to be
cleaned up in order to allow me to address an issue in the ATR code.

Finally the ixgbe ATR code has been generating bogus rules for a while now
when raw sockets are being used.  The last patch resolves this and cleans
up the IPv6 extended header parsing to match the approach taken for i40e.

---

Alexander Duyck (3):
      i40e: Add support for ATR w/ IPv6 extension headers
      ixgbe: Store VXLAN port number in network order
      ixgbe: Fix ATR so that it correctly handles IPv6 extension headers


 drivers/net/ethernet/intel/i40e/i40e_txrx.c   |   30 ++++----
 drivers/net/ethernet/intel/ixgbe/ixgbe.h      |    8 +-
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c |   90 ++++++++-----------------
 3 files changed, 44 insertions(+), 84 deletions(-)

--

             reply	other threads:[~2016-01-26  3:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  3:31 Alexander Duyck [this message]
2016-01-26  3:32 ` [Intel-wired-lan] [next PATCH 1/3] i40e: Add support for ATR w/ IPv6 extension headers Alexander Duyck
2016-01-27 18:49   ` Bowers, AndrewX
2016-01-26  3:36 ` [Intel-wired-lan] [next PATCH 2/3] ixgbe: Store VXLAN port number in network order Alexander Duyck
2016-03-01 18:23   ` Bowers, AndrewX
2016-01-26  3:39 ` [Intel-wired-lan] [next PATCH 3/3] ixgbe: Fix ATR so that it correctly handles IPv6 extension headers Alexander Duyck
2016-03-01 19:10   ` Bowers, AndrewX

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=20160126032616.16387.86351.stgit@localhost.localdomain \
    --to=aduyck@mirantis.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