<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
</div>
<blockquote type="cite"
cite="mid:CAA6-MF_yzAj5-+D6K_H9GaQRaZLLW0D2a88FQnMmwO66+=O67g@mail.gmail.com">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
As the above shows, WG threads are already bound to a particular
CPU and this<br>
can't be changed.<br>
</blockquote>
<div><br>
</div>
<div>Right, my bad. </div>
</blockquote>
<p>OK. So we have N kernel threads (one per CPU) and one CPU that
really shouldn't do anything but interrupt processing.</p>
<p>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.</p>
<p>We could then set the network interface's IRQ affinity to one of
the "free" CPUs, and we'd be all set.</p>
<pre class="moz-signature" cols="72">--
-- mit freundlichen Grüßen
--
-- Matthias Urlichs</pre>
</body>
</html>