wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: paul@mjr.org
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 23:12:21 +0200	[thread overview]
Message-ID: <CAHmME9rqOp5F2BmSHPM01HtuPQSAGcA_hECZCSFN5UPckRGaaQ@mail.gmail.com> (raw)
In-Reply-To: <98f37803e752f4d4f19b9064240f0b876b2db588.camel@mjr.org>

On Wed, Jun 13, 2018 at 4:54 PM Paul Hedderly <paul@mjr.org> wrote:
> Yea that performance hit is a nuisance

I find that doubtful, for the reasons Greg mentioned.

But in either case, I don't anticipate this will be the final
situation, but rather just a stop gap measure. I think we'll be ready
to revisit this after working on some other related FPU changes. And
for the time being, this at least fixes the crashes.

  parent reply	other threads:[~2018-06-13 21:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 20:00 Kernel lockup with (debian) 4.16.0-2-rt-amd64 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
2018-06-13 15:08               ` Greg KH
2018-06-13 16:07                 ` Paul Hedderly
2018-06-13 21:12               ` Jason A. Donenfeld [this message]
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=CAHmME9rqOp5F2BmSHPM01HtuPQSAGcA_hECZCSFN5UPckRGaaQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=paul@mjr.org \
    --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).