Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Paul Hedderly <paul@mjr.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel lockup with (debian) 4.16.0-2-rt-amd64
Date: Wed, 13 Jun 2018 15:54:24 +0100	[thread overview]
Message-ID: <98f37803e752f4d4f19b9064240f0b876b2db588.camel@mjr.org> (raw)
In-Reply-To: <CAHmME9okF00z8-9xPU=dm_vOrdf5gv4D+CpWtVXdu2oW+N-7zw@mail.gmail.com>

On Wed, 2018-06-13 at 15:52 +0200, Jason A. Donenfeld wrote:
> Hi Paul,
> 
> I got an -rt kernel up and running, enabled a bunch of nice debugging
> options, and found a handful of problems, all of which were fixed by:
> https://git.zx2c4.com/WireGuard/commit/?id=0f05452d043d8d047cf5d7987f
> c2732b97d676e6
> 
> I realize the solution in that patch is a bit of a bummer, but at the
> very least it keeps things from breaking now. I'll see if I can
> improve it somewhere down the line.

OUch. "So on sane kernels" I guess RT isn't sane then!

Yea that performance hit is a nuisance, although in reality when I
really need RT I wont be doing much over a VPN... so I may have to suck
up to rebooting between kernels for a while. No big deal.

Thanks again - I will test that new patch later.

  reply	other threads:[~2018-06-13 14:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 20:00 Paul Hedderly
2018-06-12 21:35 ` Jason A. Donenfeld
2018-06-12 21:42   ` Paul Hedderly
2018-06-12 21:47   ` Jason A. Donenfeld
2018-06-13  1:58     ` Jason A. Donenfeld
2018-06-13  7:58       ` Paul Hedderly
2018-06-13 12:13         ` Jason A. Donenfeld
2018-06-13 13:52           ` Jason A. Donenfeld
2018-06-13 14:54             ` Paul Hedderly [this message]
2018-06-13 15:08               ` Greg KH
2018-06-13 16:07                 ` Paul Hedderly
2018-06-13 21:12               ` Jason A. Donenfeld
2018-06-14 19:49             ` Paul Hedderly
2018-06-15 17:04               ` Jason A. Donenfeld
2018-06-13 14:49           ` Paul Hedderly
2018-06-12 21:38 ` Paul Hedderly

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=98f37803e752f4d4f19b9064240f0b876b2db588.camel@mjr.org \
    --to=paul@mjr.org \
    --cc=Jason@zx2c4.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).