From: Haifeng Xu <haifeng.xu@shopee.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
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: Thu, 2 Jan 2025 16:43:18 +0800 [thread overview]
Message-ID: <c2c94aa3-c557-4a74-82fc-d88821522a8f@shopee.com> (raw)
In-Reply-To: <CANn89iKVVS=ODm9jKnwG0d_FNUJ7zdYxeDYDyyOb74y3ELJLdA@mail.gmail.com>
On 2025/1/2 16:13, Eric Dumazet wrote:
> On Thu, Jan 2, 2025 at 4:53 AM Haifeng Xu <haifeng.xu@shopee.com> wrote:
>>
>> Hi masters,
>>
>> We use the Intel Corporation 82599ES NIC in our production environment. And it has 63 rx queues, every rx queue interrupt is processed by a single cpu.
>> The RSS configuration can be seen as follow:
>>
>> RX flow hash indirection table for eno5 with 63 RX ring(s):
>> 0: 0 1 2 3 4 5 6 7
>> 8: 8 9 10 11 12 13 14 15
>> 16: 0 1 2 3 4 5 6 7
>> 24: 8 9 10 11 12 13 14 15
>> 32: 0 1 2 3 4 5 6 7
>> 40: 8 9 10 11 12 13 14 15
>> 48: 0 1 2 3 4 5 6 7
>> 56: 8 9 10 11 12 13 14 15
>> 64: 0 1 2 3 4 5 6 7
>> 72: 8 9 10 11 12 13 14 15
>> 80: 0 1 2 3 4 5 6 7
>> 88: 8 9 10 11 12 13 14 15
>> 96: 0 1 2 3 4 5 6 7
>> 104: 8 9 10 11 12 13 14 15
>> 112: 0 1 2 3 4 5 6 7
>> 120: 8 9 10 11 12 13 14 15
>>
>> The maximum number of RSS queues is 16. So I have some questions about this. Will other cpus except 0~15 receive the rx interrupts?
>>
>> In our production environment, cpu 16~62 also receive the rx interrupts. Was our RSS misconfigured?
>
> It really depends on which cpus are assigned to each IRQ.
>
Hi Eric,
Each irq was assigned to a single cpu, for exapmle:
irq cpu
117 0
118 1
......
179 62
All cpus trigger interrupts not only cpus 0~15.
It seems that the result is inconsistent with the RSS hash value.
Thanks!
> Look at /proc/irq/{IRQ_NUM}/smp_affinity
>
> Also you can have some details in Documentation/networking/scaling.rst
next prev parent reply other threads:[~2025-01-02 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 3:53 Haifeng Xu
2025-01-02 8:13 ` Eric Dumazet
2025-01-02 8:43 ` Haifeng Xu [this message]
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
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=c2c94aa3-c557-4a74-82fc-d88821522a8f@shopee.com \
--to=haifeng.xu@shopee.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=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
all inboxes | Powered by JetHome®