From: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
To: "magnus.karlsson@gmail.com" <magnus.karlsson@gmail.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"brouer@redhat.com" <brouer@redhat.com>
Subject: Re: [PATCH intel-net 0/5] i40e: ice: ixgbe: ixgbevf: igb: add correct exception tracing for XDP
Date: Fri, 7 May 2021 22:58:42 +0000 [thread overview]
Message-ID: <75d0a1d13a755bc128458c0d43f16d54fe08051e.camel@intel.com> (raw)
In-Reply-To: <20210423100446.15412-1-magnus.karlsson@gmail.com>
On Fri, 2021-04-23 at 12:04 +0200, Magnus Karlsson wrote:
> 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.
>
> Thanks: Magnus
This doesn't apply anymore with the 5.13 patches. It looks like your
"optimize for XDP_REDIRECT in xsk path" patches are conflicting with
some of these. Did you want to rework them?
Thanks,
Tony
> Magnus Karlsson (5):
> 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
>
> drivers/net/ethernet/intel/i40e/i40e_txrx.c | 7 ++++++-
> drivers/net/ethernet/intel/i40e/i40e_xsk.c | 7 ++++++-
> drivers/net/ethernet/intel/ice/ice_txrx.c | 12 +++++++++---
> drivers/net/ethernet/intel/ice/ice_xsk.c | 7 ++++++-
> drivers/net/ethernet/intel/igb/igb_main.c | 10 ++++++----
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 16 ++++++++----
> ----
> drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c | 13 ++++++++-----
> .../net/ethernet/intel/ixgbevf/ixgbevf_main.c | 3 +++
> 8 files changed, 52 insertions(+), 23 deletions(-)
>
>
> base-commit: bb556de79f0a9e647e8febe15786ee68483fa67b
> --
> 2.29.0
next prev parent reply other threads:[~2021-05-07 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 10:04 [PATCH intel-net 0/5] i40e: ice: ixgbe: ixgbevf: igb: add correct exception tracing for XDP Magnus Karlsson
2021-04-23 10:04 ` [PATCH intel-net 1/5] i40e: " Magnus Karlsson
2021-04-23 10:04 ` [PATCH intel-net 2/5] ice: " Magnus Karlsson
2021-04-23 10:04 ` [PATCH intel-net 3/5] ixgbe: " Magnus Karlsson
2021-05-21 11:39 ` [Intel-wired-lan] " Jambekar, Vishakha
2021-04-23 10:04 ` [PATCH intel-net 4/5] igb " Magnus Karlsson
2021-04-23 10:04 ` [PATCH intel-net 5/5] ixgbevf: " Magnus Karlsson
2021-05-07 22:58 ` Nguyen, Anthony L [this message]
2021-05-10 6:06 ` [PATCH intel-net 0/5] i40e: ice: ixgbe: ixgbevf: igb: " Magnus Karlsson
2021-05-10 8:57 ` Jesper Dangaard Brouer
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=75d0a1d13a755bc128458c0d43f16d54fe08051e.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=brouer@redhat.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@gmail.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).