From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: nicolas prochazka <prochazka.nicolas@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: multiple wireguard interface and kworker ressources
Date: Wed, 14 Jun 2017 16:13:15 +0200 [thread overview]
Message-ID: <CAHmME9rh4aHp2z0RLb8VVEJ=HQjT=vd5ib-D3d_tCSNjZ-7xzg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oOmacx7hhjr-5ER3mxHaACvsT7v0wuyfBPZuy5K7Bk2A@mail.gmail.com>
On Wed, Jun 14, 2017 at 4:05 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Will keep a kworker at 100% CPU, even after that command completes?
> I'm unable to reproduce this here. Could you give me detailed
> environmental information so that I can reproduce this precisely?
> Something minimal and easily reproducable would be preferred.
Okay, I have a working reproducer now, and I've isolated the issue to
the xt_hashlimit garbage collector, an issue outside the WireGuard
code base. I might look for a work around within WireGuard, however.
I'll keep you posted.
next prev parent reply other threads:[~2017-06-14 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:38 nicolas prochazka
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 [this message]
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='CAHmME9rh4aHp2z0RLb8VVEJ=HQjT=vd5ib-D3d_tCSNjZ-7xzg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=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).