From: "Jambekar, Vishakha" <vishakha.jambekar@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 4/6] igb: add correct exception tracing for XDP
Date: Fri, 21 May 2021 11:44:54 +0000 [thread overview]
Message-ID: <SA2PR11MB4940856C4DD29124DACB6654FF299@SA2PR11MB4940.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210510093854.31652-5-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 4/6] igb: 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: 9cbc948b5a20 ("igb: add XDP support")
> Reported-by: Jesper Dangaard Brouer <brouer@redhat.com>
> Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
Tested-by: Vishakha Jambekar<vishakha.jambekar@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jambekar, Vishakha <vishakha.jambekar@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH intel-net v2 4/6] igb: add correct exception tracing for XDP
Date: Fri, 21 May 2021 11:44:54 +0000 [thread overview]
Message-ID: <SA2PR11MB4940856C4DD29124DACB6654FF299@SA2PR11MB4940.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210510093854.31652-5-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 at lists.osuosl.org; Nguyen, Anthony L <anthony.l.nguyen@intel.com>;
> Fijalkowski, Maciej <maciej.fijalkowski@intel.com>
> Cc: netdev at vger.kernel.org; brouer at redhat.com
> Subject: [Intel-wired-lan] [PATCH intel-net v2 4/6] igb: 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: 9cbc948b5a20 ("igb: add XDP support")
> Reported-by: Jesper Dangaard Brouer <brouer@redhat.com>
> Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
Tested-by: Vishakha Jambekar<vishakha.jambekar@intel.com>
next prev parent reply other threads:[~2021-05-21 11:45 UTC|newest]
Thread overview: 28+ 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 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-10 9:38 ` [PATCH intel-net v2 1/6] i40e: " Magnus Karlsson
2021-05-10 9:38 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-19 16:12 ` Bhandare, KiranX
2021-05-19 16:12 ` Bhandare, KiranX
2021-05-10 9:38 ` [PATCH intel-net v2 2/6] ice: " Magnus Karlsson
2021-05-10 9:38 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-19 16:14 ` Bhandare, KiranX
2021-05-19 16:14 ` Bhandare, KiranX
2021-05-10 9:38 ` [PATCH intel-net v2 3/6] ixgbe: " Magnus Karlsson
2021-05-10 9:38 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-28 4:16 ` Jambekar, Vishakha
2021-05-28 4:16 ` Jambekar, Vishakha
2021-05-10 9:38 ` [PATCH intel-net v2 4/6] igb: " Magnus Karlsson
2021-05-10 9:38 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-21 11:44 ` Jambekar, Vishakha [this message]
2021-05-21 11:44 ` Jambekar, Vishakha
2021-05-10 9:38 ` [PATCH intel-net v2 5/6] ixgbevf: " Magnus Karlsson
2021-05-10 9:38 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-21 11:42 ` Jambekar, Vishakha
2021-05-21 11:42 ` Jambekar, Vishakha
2021-05-10 9:38 ` [PATCH intel-net v2 6/6] igc: " Magnus Karlsson
2021-05-10 9:38 ` [Intel-wired-lan] " Magnus Karlsson
2021-05-24 10:05 ` Dvora Fuxbrumer
2021-05-24 10:05 ` Dvora Fuxbrumer
2021-05-24 10:08 ` 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=SA2PR11MB4940856C4DD29124DACB6654FF299@SA2PR11MB4940.namprd11.prod.outlook.com \
--to=vishakha.jambekar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.