From: nicolas prochazka <prochazka.nicolas@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: multiple wireguard interface and kworker ressources
Date: Tue, 13 Jun 2017 14:38:09 +0200 [thread overview]
Message-ID: <CADdae-jBtz7zfMRPkS3c2n_zG+LCuN_0iUZHCSM=H8dWdDBUUw@mail.gmail.com> (raw)
Hello,
for i in `seq 1 1000` ; do ip link add dev wg${i} type wireguard ; done
=> kernel thread kworker is 50% cpu time , with 5000 interface ,
100% cpu time
for i in `seq 1 1000` ; do ip link add dev ifb${i} type ifb ; done
( ifb or dummy .. )
=> kernel thread kworker is < 1%
Is it normal behavior ?
Version : WireGuard 0.0.20170409
kernel : 4.9.23
Regards,
Nicolas Prochazka
next reply other threads:[~2017-06-13 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:38 nicolas prochazka [this message]
2017-06-13 12:48 ` Jason A. Donenfeld
2017-06-13 14:55 ` nicolas prochazka
2017-06-13 21:47 ` Jason A. Donenfeld
2017-06-14 7:52 ` nicolas prochazka
2017-06-14 13:50 ` nicolas prochazka
2017-06-14 14:15 ` Jason A. Donenfeld
2017-06-14 18:08 ` nicolas prochazka
2017-06-21 13:54 ` Jason A. Donenfeld
2017-06-14 14:05 ` Jason A. Donenfeld
2017-06-14 14:13 ` Jason A. Donenfeld
2017-06-14 14:17 ` nicolas prochazka
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='CADdae-jBtz7zfMRPkS3c2n_zG+LCuN_0iUZHCSM=H8dWdDBUUw@mail.gmail.com' \
--to=prochazka.nicolas@gmail.com \
--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).