public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Haifeng Xu <haifeng.xu@shopee.com>,
	Edward Cree <ecree.xilinx@gmail.com>,
	Eric Dumazet <edumazet@google.com>,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
	"Kwapulinski, Piotr" <piotr.kwapulinski@intel.com>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Question] ixgbe:Mechanism of RSS
Date: Wed, 8 Jan 2025 13:06:20 -0800	[thread overview]
Message-ID: <bb5dbf24-ef80-4220-8b07-40eed9ac15ae@intel.com> (raw)
In-Reply-To: <1ade15b1-f533-4cc6-8522-2d725532e251@shopee.com>



On 1/7/2025 7:36 PM, Haifeng Xu wrote:
> 
> 
> On 2025/1/8 01:16, Tony Nguyen wrote:

...

>>
>> What's your ntuple filter setting? If it's off, I suspect it may be the Flow Director ATR (Application Targeting Routing) feature which will utilize all queues. I believe if you turn on ntuple filters this will turn that feature off.
> 
> Yes, our ntuple filter setting is off. After turning on the ntuple filters, I compare the delta of recieved packets,
> only 0~15 rx rings are non-zero, other rx rings are zero.
> 
> If we want to spread the packets across 0~62, how can we tune the NIC setting?
> we have enabled 63 rx queues, irq_affinity and rx-flow-hash, but the 0~15 cpu
> received more packets than others.

As Jakub mentioned earlier, HW RSS is only supported on this device for 
16 queues. ATR will steer bi-directional traffic to utilize additional 
queues, however, once its exhausted it will fallback to RSS, which is 
why CPUs 0-15 are receiving more traffic than the others. I'm not aware 
of a way to evenly spread the traffic beyond the 16 HW supported RSS 
queues for this device.

Thanks,
Tony

> Thanks!



  reply	other threads:[~2025-01-08 21:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02  3:53 [Question] ixgbe:Mechanism of RSS Haifeng Xu
2025-01-02  8:13 ` Eric Dumazet
2025-01-02  8:43   ` Haifeng Xu
2025-01-02 10:34     ` Eric Dumazet
2025-01-02 11:23       ` Haifeng Xu
2025-01-02 11:46         ` Eric Dumazet
2025-01-03  2:36           ` Haifeng Xu
2025-01-02 16:01         ` Edward Cree
2025-01-02 16:39           ` Jakub Kicinski
2025-01-03  2:37             ` Haifeng Xu
2025-01-03  3:05           ` Haifeng Xu
2025-01-07 17:16             ` Tony Nguyen
2025-01-08  3:36               ` Haifeng Xu
2025-01-08 21:06                 ` Tony Nguyen [this message]
2025-01-09  3:26                   ` Haifeng Xu

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=bb5dbf24-ef80-4220-8b07-40eed9ac15ae@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=haifeng.xu@shopee.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=piotr.kwapulinski@intel.com \
    --cc=przemyslaw.kitszel@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