From: Simon Horman <horms@kernel.org>
To: Suresh Kumar <suresh2514@gmail.com>
Cc: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i40e: print correct hw max rss count in kernel ring buffer
Date: Fri, 19 Jan 2024 14:49:26 +0000 [thread overview]
Message-ID: <20240119144926.GA89683@kernel.org> (raw)
In-Reply-To: <20240119131652.8050-1-suresh2514@gmail.com>
On Fri, Jan 19, 2024 at 06:46:52PM +0530, Suresh Kumar wrote:
> The value printed for "HW max RSS count" is wrong in kernel dmesg for i40e
> NICs:
>
> ... i40e 0000:63:00.0: User requested queue count/HW max RSS count: 48/64
>
> whereas ethtool reports the correct value from "vsi->num_queue_pairs"
>
> Channel parameters for eno33:
> Pre-set maximums:
> RX: n/a
> TX: n/a
> Other: 1
> Combined: 96
> Current hardware settings:
> RX: n/a
> TX: n/a
> Other: 1
> Combined: 96 <-------
>
> and is misleading.
>
> This value is printed from 'pf->rss_size_max' which seems hardcoded.
>
> Below commit also removed this 64 limit:
>
> Commit e56afa599609d3afe8b0ce24b553ab95e9782502
> Author: Amritha Nambiar <amritha.nambiar@intel.com>
> Date: Wed Nov 8 16:38:43 2017 -0800
>
> i40e: Remove limit of 64 max queues per channel
Hi Suresh,
I think it would be more normal to cite this commit something like this:
The limit of 64 was removed by
commit e56afa599609 ("i40e: Remove limit of 64 max queues per channel")
Also, it's not clear to me if this should be considered a fix or not.
If not, which I lean towards, then it should probably be targeted
at iwl-next.
Subject: [PATCH iwl-next] ...
If it is a fix, then it should have a Fixes tag and probably
be targeted at iwl.
Subject: [PATCH iwl] ...
...
prev parent reply other threads:[~2024-01-19 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 13:16 [PATCH] i40e: print correct hw max rss count in kernel ring buffer Suresh Kumar
2024-01-19 14:49 ` Simon Horman [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=20240119144926.GA89683@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=suresh2514@gmail.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;
as well as URLs for NNTP newsgroup(s).