lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87e945f6-2811-0ddb-1666-06accd126efb@gmail.com>
Date: Thu, 2 Jan 2025 16:01:18 +0000
From: Edward Cree <ecree.xilinx@...il.com>
To: Haifeng Xu <haifeng.xu@...pee.com>, Eric Dumazet <edumazet@...gle.com>
Cc: Tony Nguyen <anthony.l.nguyen@...el.com>,
 Przemek Kitszel <przemyslaw.kitszel@...el.com>,
 "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>, linux-kernel@...r.kernel.org,
 netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org
Subject: Re: [Question] ixgbe:Mechanism of RSS

On 02/01/2025 11:23, Haifeng Xu wrote:
> We want to make full use of cpu resources to receive packets. So
> we enable 63 rx queues. But we found the rate of interrupt growth
> on cpu 0~15 is faster than other cpus(almost twice).
...
> I am confused that why ixgbe NIC can dispatch the packets
> to the rx queues that not specified in RSS configuration.

Hypothesis: it isn't doing so, RX is only happening on cpus (and
 queues) 0-15, but the other CPUs are still sending traffic and
 thus getting TX completion interrupts from their TX queues.
`ethtool -S` output has per-queue traffic stats which should
 confirm this.

(But Eric is right that if you _want_ RX to use every CPU you
 should just change the indirection table.)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ