From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Speed on Raspberry Pi 4
Date: Thu, 18 Jul 2019 10:15:22 +0200 [thread overview]
Message-ID: <e974e0bd-9a84-f725-d5e9-36f56c25707b@urlichs.de> (raw)
In-Reply-To: <CAA6-MF_yzAj5-+D6K_H9GaQRaZLLW0D2a88FQnMmwO66+=O67g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]
Hi,
>
> As the above shows, WG threads are already bound to a particular
> CPU and this
> can't be changed.
>
>
> Right, my bad.
OK. So we have N kernel threads (one per CPU) and one CPU that really
shouldn't do anything but interrupt processing.
That looks like we need an option to limit wireguard to a specific set
of CPUs. That'd be a good option to have in any case, because we don't
want the poor Raspberry Pi (or any other semi-underpowered machine) to
starve everything else when it gets flooded with more wireguard work
than it can handle.
We could then set the network interface's IRQ affinity to one of the
"free" CPUs, and we'd be all set.
--
-- mit freundlichen Grüßen
--
-- Matthias Urlichs
[-- Attachment #1.2: Type: text/html, Size: 1378 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-07-18 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 10:38 Speed on Raspberry Pi 4 Christopher Bachner
2019-07-17 20:50 ` Roman Mamedov
2019-07-18 6:38 ` Janne Johansson
2019-07-18 6:56 ` Roman Mamedov
2019-07-18 8:01 ` Janne Johansson
2019-07-18 8:15 ` Matthias Urlichs [this message]
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=e974e0bd-9a84-f725-d5e9-36f56c25707b@urlichs.de \
--to=matthias@urlichs.de \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).