From: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
To: "Gomes, Vinicius" <vinicius.gomes@intel.com>,
"kurt@linutronix.de" <kurt@linutronix.de>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"andre.guedes@intel.com" <andre.guedes@intel.com>,
"Joseph, Jithu" <jithu.joseph@intel.com>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"hawk@kernel.org" <hawk@kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"vedang.patel@intel.com" <vedang.patel@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] igc: Clear old XDP info when changing ring settings
Date: Fri, 4 Feb 2022 17:04:58 +0000 [thread overview]
Message-ID: <0f1e1c0fc4f555ef0eaaa983da6d8f012a0acf60.camel@intel.com> (raw)
In-Reply-To: <20220204080217.70054-1-kurt@linutronix.de>
Hi Kurt,
On Fri, 2022-02-04 at 09:02 +0100, Kurt Kanzenbach wrote:
> When changing ring sizes the driver triggers kernel warnings in XDP
> code.
>
> For instance, running 'ethtool -G $interface tx 1024 rx 1024' yields:
>
> > [ 754.838136] Missing unregister, handled but fix driver
> > [ 754.838143] WARNING: CPU: 4 PID: 704 at net/core/xdp.c:170
> > xdp_rxq_info_reg+0x7d/0xe0
>
> The newly allocated ring is copied by memcpy() and still contains the
> old XDP
> information. Therefore, it has to be cleared before allocating new
> resources
> by igc_setup_rx_resources().
>
> Igb does it the same way. Keep the code in sync.
Thanks for the patch, but we have a patch[1] to resolve this issue in a
more preferred method. igb is actually changing as well to this new
solution [2].
Thanks,
Tony
[1] https://patchwork.ozlabs.org/patch/1581816/
[2] https://patchwork.ozlabs.org/patch/1581815/
> Fixes: 4609ffb9f615 ("igc: Refactor XDP rxq info registration")
> Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
next prev parent reply other threads:[~2022-02-04 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:02 [PATCH net] igc: Clear old XDP info when changing ring settings Kurt Kanzenbach
2022-02-04 17:04 ` Nguyen, Anthony L [this message]
2022-02-05 9:57 ` Kurt Kanzenbach
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=0f1e1c0fc4f555ef0eaaa983da6d8f012a0acf60.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=andre.guedes@intel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jithu.joseph@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vedang.patel@intel.com \
--cc=vinicius.gomes@intel.com \
/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