From: Janne Johansson <icepic.dz@gmail.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Christopher Bachner <hello@chrisbox.org>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Speed on Raspberry Pi 4
Date: Thu, 18 Jul 2019 10:01:31 +0200 [thread overview]
Message-ID: <CAA6-MF_yzAj5-+D6K_H9GaQRaZLLW0D2a88FQnMmwO66+=O67g@mail.gmail.com> (raw)
In-Reply-To: <20190718115614.60b7927a@natsu>
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
Den tors 18 juli 2019 kl 08:56 skrev Roman Mamedov <rm@romanrm.net>:
> On Thu, 18 Jul 2019 08:38:54 +0200
> Janne Johansson <icepic.dz@gmail.com> wrote:
>
> > With taskset you should be able to:
> > https://www.howtoforge.com/linux-taskset-command/
>
> It appears "taskset" only works on regular programs, not kernel threads:
>
> # taskset -p -c 1 2128
> pid 2128's current affinity list: 0
> taskset: failed to set pid 2128's affinity: Invalid argument
>
> # taskset -p -c 1 2129
> pid 2129's current affinity list: 1
> taskset: failed to set pid 2129's affinity: Invalid argument
>
> As the above shows, WG threads are already bound to a particular CPU and
> this
> can't be changed.
>
Right, my bad.
--
May the most significant bit of your life be positive.
[-- Attachment #1.2: Type: text/html, Size: 1406 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-07-18 8:01 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 [this message]
2019-07-18 8:15 ` Matthias Urlichs
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='CAA6-MF_yzAj5-+D6K_H9GaQRaZLLW0D2a88FQnMmwO66+=O67g@mail.gmail.com' \
--to=icepic.dz@gmail.com \
--cc=hello@chrisbox.org \
--cc=rm@romanrm.net \
--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).