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
| ||
|
Message-ID: <f436c2cc-4f6f-0dc1-a343-4c41eb14935e@nbd.name> Date: Tue, 28 Mar 2023 11:46:03 +0200 From: Felix Fietkau <nbd@....name> To: Jakub Kicinski <kuba@...nel.org> Cc: netdev@...r.kernel.org, Jonathan Corbet <corbet@....net>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next] net/core: add optional threading for backlog processing On 28.03.23 04:06, Jakub Kicinski wrote: > On Sat, 25 Mar 2023 06:42:43 +0100 Felix Fietkau wrote: >> >> In my tests it brings down latency (both avg and p99) considerably in >> >> some cases. I posted some numbers here: >> >> https://lore.kernel.org/netdev/e317d5bc-cc26-8b1b-ca4b-66b5328683c4@nbd.name/ >> > >> > Could you provide the full configuration for this test? >> > In non-threaded mode the RPS is enabled to spread over remaining >> > 3 cores? >> >> In this test I'm using threaded NAPI and backlog_threaded without any >> fixed core assignment. > > I was asking about the rps_threaded=0 side of the comparison. > So you're saying on that side you were using threaded NAPI with > no pinning and RPS across all cores? Yes. - Felix
Powered by blists - more mailing lists