From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Jakub Kicinski'" <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, <mengyuanlou@net-swift.com>,
<stable@vger.kernel.org>
Subject: RE: [PATCH] net: libwx: fix the incorrect display of the queue number
Date: Tue, 1 Jul 2025 15:02:07 +0800 [thread overview]
Message-ID: <050201dbea56$0f357410$2da05c30$@trustnetic.com> (raw)
In-Reply-To: <20250630183127.0eea7b0b@kernel.org>
On Tue, Jul 1, 2025 9:31 AM, Jakub Kicinski wrote:
> On Fri, 27 Jun 2025 16:09:38 +0800 Jiawen Wu wrote:
> > When setting "ethtool -L eth0 combined 1", the number of RX/TX queue is
> > changed to be 1. RSS is disabled at this moment, and the indices of FDIR
> > have not be changed in wx_set_rss_queues(). So the combined count still
> > shows the previous value. This issue was introduced when supporting
> > FDIR. Fix it for those devices that support FDIR.
>
> Why are you hacking up the get_channels rather than making _F_FDIR be
> sane in all situations? I mean why not:
>
> --- a/drivers/net/ethernet/wangxun/libwx/wx_lib.c
> +++ b/drivers/net/ethernet/wangxun/libwx/wx_lib.c
> @@ -1709,6 +1709,7 @@ static void wx_set_rss_queues(struct wx *wx)
> * distribution of flows across cores, even when an FDIR flow
> * isn't matched.
> */
> + wx->ring_feature[RING_F_FDIR].indices = 1;
> if (f->indices > 1) {
> f = &wx->ring_feature[RING_F_FDIR];
>
> ?
This is quite reasonable, thanks.
prev parent reply other threads:[~2025-07-01 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 8:09 [PATCH] net: libwx: fix the incorrect display of the queue number Jiawen Wu
2025-06-27 19:07 ` Simon Horman
2025-07-01 1:31 ` Jakub Kicinski
2025-07-01 7:02 ` Jiawen Wu [this message]
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='050201dbea56$0f357410$2da05c30$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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).