From: "Bhandare, KiranX" <kiranx.bhandare@intel.com>
To: Magnus Karlsson <magnus.karlsson@gmail.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@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: [Intel-wired-lan] [PATCH intel-net v2 1/6] i40e: add correct exception tracing for XDP
Date: Wed, 19 May 2021 16:12:27 +0000 [thread overview]
Message-ID: <DM6PR11MB3292834F3FBC9AE8D4F6FD0BF12B9@DM6PR11MB3292.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210510093854.31652-2-magnus.karlsson@gmail.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Magnus Karlsson
> Sent: Monday, May 10, 2021 3:09 PM
> To: Karlsson, Magnus <magnus.karlsson@intel.com>; intel-wired-
> lan@lists.osuosl.org; Nguyen, Anthony L <anthony.l.nguyen@intel.com>;
> Fijalkowski, Maciej <maciej.fijalkowski@intel.com>
> Cc: netdev@vger.kernel.org; brouer@redhat.com
> Subject: [Intel-wired-lan] [PATCH intel-net v2 1/6] i40e: add correct exception
> tracing for XDP
>
> From: Magnus Karlsson <magnus.karlsson@intel.com>
>
> 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.
>
> Fixes: 74608d17fe29 ("i40e: add support for XDP_TX action")
> Fixes: 0a714186d3c0 ("i40e: add AF_XDP zero-copy Rx support")
> Reported-by: Jesper Dangaard Brouer <brouer@redhat.com>
> Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_txrx.c | 7 ++++++-
> drivers/net/ethernet/intel/i40e/i40e_xsk.c | 8 ++++++--
> 2 files changed, 12 insertions(+), 3 deletions(-)
>
Tested-by: Kiran Bhandare <kiranx.bhandare@intel.com> A Contingent Worker at Intel
next prev parent reply other threads:[~2021-05-19 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 9:38 [PATCH intel-net v2 0/6] i40e: ice: ixgbe: ixgbevf: igb: igc: add correct exception tracing for XDP Magnus Karlsson
2021-05-10 9:38 ` [PATCH intel-net v2 1/6] i40e: " Magnus Karlsson
2021-05-19 16:12 ` Bhandare, KiranX [this message]
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=DM6PR11MB3292834F3FBC9AE8D4F6FD0BF12B9@DM6PR11MB3292.namprd11.prod.outlook.com \
--to=kiranx.bhandare@intel.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@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).