netdev - Re: Optimizing kernel compilation / alignments for network performance

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: <CAK8P3a3=64B7er2QiCBBcskjxbiiG2-fDCpDWR8OD15v9GiOVQ@mail.gmail.com>
Date:   Tue, 10 May 2022 15:19:32 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Rafał Miłecki <zajec5@...il.com>
Cc:     Arnd Bergmann <arnd@...db.de>, Andrew Lunn <andrew@...n.ch>,
        Alexander Lobakin <alexandr.lobakin@...el.com>,
        Network Development <netdev@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Russell King <linux@...linux.org.uk>,
        Felix Fietkau <nbd@....name>,
        "openwrt-devel@...ts.openwrt.org" <openwrt-devel@...ts.openwrt.org>,
        Florian Fainelli <f.fainelli@...il.com>
Subject: Re: Optimizing kernel compilation / alignments for network performance

On Tue, May 10, 2022 at 2:51 PM Rafał Miłecki <zajec5@...il.com> wrote:
> On 6.05.2022 11:44, Arnd Bergmann wrote:
>
> My router has a single swtich so I use two VLANs:
> eth0.1 - LAN
> eth0.2 - WAN
> (VLAN traffic is routed to correct ports by switch). On top of that I
> have "br-lan" bridge interface briding eth0.1 and wireless interfaces.
>
> For all that time I had /sys/class/net/br-lan/queues/rx-0/rps_cpus set
> to 3. So bridge traffic was randomly handled by CPU 0 or CPU 1.
>
> So if I assign specific CPU core to each of two interfaces, e.g.:
> echo 1 > /sys/class/net/eth0/queues/rx-0/rps_cpus
> echo 2 > /sys/class/net/br-lan/queues/rx-0/rps_cpus
> things get stable.
>
> With above I get stable 419 Mb/s (CPUs load: 100% + 64%) on every iperf
> session.

Ah, very nice! One part of the mystery is solved then I guess.

       Arnd