From: Haifeng Xu <haifeng.xu@shopee.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>, ",
Przemek Kitszel" <przemyslaw.kitszel@intel.com>, ",
\"David S. Miller\"" <davem@davemloft.net>, ",
Eric Dumazet" <edumazet@google.com>, ",
Jakub Kicinski" <kuba@kernel.org>, ",
Paolo Abeni" <pabeni@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: [Question] ixgbe:Mechanism of RSS
Date: Thu, 2 Jan 2025 11:53:05 +0800 [thread overview]
Message-ID: <da83df12-d7e2-41fe-a303-290640e2a4a4@shopee.com> (raw)
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?
next reply other threads:[~2025-01-02 3:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 3:53 Haifeng Xu [this message]
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
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=da83df12-d7e2-41fe-a303-290640e2a4a4@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®