Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Erik Schuitema <erik@essd.nl>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: "BUG: scheduling while atomic" on 5.4 kernels with PREEMPT_RT
Date: Mon, 8 Feb 2021 12:36:36 +0100	[thread overview]
Message-ID: <0d84e883-2aa5-df3c-95bd-24304223d07f@essd.nl> (raw)
In-Reply-To: <CAHmME9pjcBFBQM67iTOjG+HLH8OnMUhxNOX2rne2umiNW9bHew@mail.gmail.com>

Hi Jason,

(Sorry for the delay in my reply..)

On 19/12/2020 19:16, Jason A. Donenfeld wrote:
 > So far as I can tell, upstream is fine with this. I'd encourage you to
 > move to the newer LTS, 5.10. The compat stuff has always been pretty
 > meh. It was an important step in getting WireGuard bootstrapped, of
 > course, but just look at this horror:
 >
 > https://git.zx2c4.com/wireguard-linux-compat/tree/src/compat/compat.h

I don't have doubts about the upstream code, I was merely wondering 
whether the performance hit from disabling SIMD is still present in 
newer kernels (it wasn't immediately obvious to me while browsing the 
5.10 source).

 > I'll keep it working as people need, but folks should really really
 > move to the new LTS, now that it's out.

These efforts are highly appreciated! It's not trivial for me to switch 
to a new kernel (needs extensive product testing), so I'm happy with the 
5.4 patch. But I'll be sure to skip right to 5.10 when moving to a new 
kernel.

Best regards,
Erik



      reply	other threads:[~2021-02-08 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 11:20 Erik Schuitema
2020-12-19 12:15 ` Jason A. Donenfeld
2020-12-19 15:32   ` Erik Schuitema
2020-12-19 18:16     ` Jason A. Donenfeld
2021-02-08 11:36       ` Erik Schuitema [this message]

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=0d84e883-2aa5-df3c-95bd-24304223d07f@essd.nl \
    --to=erik@essd.nl \
    --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).