netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Karlsson <magnus.karlsson@gmail.com>
To: magnus.karlsson@intel.com, intel-wired-lan@lists.osuosl.org,
	anthony.l.nguyen@intel.com, maciej.fijalkowski@intel.com
Cc: Magnus Karlsson <magnus.karlsson@gmail.com>,
	netdev@vger.kernel.org, brouer@redhat.com
Subject: [PATCH intel-net v2 0/6] i40e: ice: ixgbe: ixgbevf: igb: igc: add correct exception tracing for XDP
Date: Mon, 10 May 2021 11:38:48 +0200	[thread overview]
Message-ID: <20210510093854.31652-1-magnus.karlsson@gmail.com> (raw)

Add missing exception tracing to XDP when a number of different errors
can occur. The support was only partial. Several errors where not
logged which would confuse the user quite a lot not knowing where and
why the packets disappeared.

This patch set fixes this for all Intel drivers with XDP support.

v1 -> v2:
* Applied fix to new XDP support in igc driver
* Rebased on latest net

Thanks: Magnus

Magnus Karlsson (6):
  i40e: add correct exception tracing for XDP
  ice: add correct exception tracing for XDP
  ixgbe: add correct exception tracing for XDP
  igb: add correct exception tracing for XDP
  ixgbevf: add correct exception tracing for XDP
  igc: add correct exception tracing for XDP

 drivers/net/ethernet/intel/i40e/i40e_txrx.c      |  7 ++++++-
 drivers/net/ethernet/intel/i40e/i40e_xsk.c       |  8 ++++++--
 drivers/net/ethernet/intel/ice/ice_txrx.c        | 12 +++++++++---
 drivers/net/ethernet/intel/ice/ice_xsk.c         |  8 ++++++--
 drivers/net/ethernet/intel/igb/igb_main.c        | 10 ++++++----
 drivers/net/ethernet/intel/igc/igc_main.c        | 11 +++++------
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c    | 16 ++++++++--------
 drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c     | 14 ++++++++------
 .../net/ethernet/intel/ixgbevf/ixgbevf_main.c    |  3 +++
 9 files changed, 57 insertions(+), 32 deletions(-)


base-commit: b741596468b010af2846b75f5e75a842ce344a6e
--
2.29.0

             reply	other threads:[~2021-05-10  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  9:38 Magnus Karlsson [this message]
2021-05-10  9:38 ` [PATCH intel-net v2 1/6] i40e: add correct exception tracing for XDP Magnus Karlsson
2021-05-19 16:12   ` [Intel-wired-lan] " Bhandare, KiranX
2021-05-10  9:38 ` [PATCH intel-net v2 2/6] ice: " Magnus Karlsson
2021-05-19 16:14   ` [Intel-wired-lan] " Bhandare, KiranX
2021-05-10  9:38 ` [PATCH intel-net v2 3/6] ixgbe: " Magnus Karlsson
2021-05-28  4:16   ` [Intel-wired-lan] " Jambekar, Vishakha
2021-05-10  9:38 ` [PATCH intel-net v2 4/6] igb: " Magnus Karlsson
2021-05-21 11:44   ` [Intel-wired-lan] " Jambekar, Vishakha
2021-05-10  9:38 ` [PATCH intel-net v2 5/6] ixgbevf: " Magnus Karlsson
2021-05-21 11:42   ` [Intel-wired-lan] " Jambekar, Vishakha
2021-05-10  9:38 ` [PATCH intel-net v2 6/6] igc: " Magnus Karlsson
2021-05-24 10:05   ` [Intel-wired-lan] " Dvora Fuxbrumer
2021-05-24 10:08   ` Dvora Fuxbrumer

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=20210510093854.31652-1-magnus.karlsson@gmail.com \
    --to=magnus.karlsson@gmail.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=brouer@redhat.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).