From: Paul Hedderly <paul@mjr.org>
To: Greg KH <gregkh@linuxfoundation.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 17:07:32 +0100 [thread overview]
Message-ID: <6c33f2b0c40477015d0fc3a66ee33c36a150f838.camel@mjr.org> (raw)
In-Reply-To: <20180613150813.GA7789@kroah.com>
On Wed, 2018-06-13 at 17:08 +0200, Greg KH wrote:
>
> Note, the -rt kernels _always_ run slower than a non-rt kernel. Real
> time is not "faster", it is only "deterministic". And it achieves
> this
> goal at the expense of performance, which is the only way it can be
> done.
Thanks for the reminder - I do forget that and get lazy and often use
the rt all the time.
> So I recommend just trying the "normal" kernel instead, odds are it
> will
> work just fine for you, unless you have some _very_ specific max-
> bound
> latency issues.
Mostly audio/jack ie duplex 32 channels at 48k with a B* X32 mixer. To
be fair I have more issues with the disc keeping up than the kernel...
But the truth is that use takes a very small part of my time and
normally a different machine so really I should use the rt kernel less!
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2018-06-13 16:03 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
2018-06-13 15:08 ` Greg KH
2018-06-13 16:07 ` Paul Hedderly [this message]
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=6c33f2b0c40477015d0fc3a66ee33c36a150f838.camel@mjr.org \
--to=paul@mjr.org \
--cc=gregkh@linuxfoundation.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).