From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] random: use raw spinlocks for use on RT
Date: Tue, 30 Aug 2022 11:24:33 -0400 [thread overview]
Message-ID: <Yw4rsdA7xu4+UrLi@zx2c4.com> (raw)
In-Reply-To: <Yw3i2N8J7yz3jnyt@linutronix.de>
Hi Sebastian,
On Tue, Aug 30, 2022 at 12:13:44PM +0200, Sebastian Andrzej Siewior wrote:
> The first patch did so yes. The second simply retried in two secs and
> this shouldn't be problematic.
This seemed pretty bad too, because now you potentially miss up to 2
seconds of messages AND it adds more complexity.
I'm fine with changing things up to accommodate RT, but not when the
result is so obviously worse than before.
In my tests I can't see any latency difference with using raw spinlocks
in random.c. Maybe I'm doing things wrong? But I'm not seeing anything
change...
Jason
next prev parent reply other threads:[~2022-08-30 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:25 [PATCH] random: use raw spinlocks for use on RT Jason A. Donenfeld
2022-08-01 14:34 ` Sebastian Andrzej Siewior
2022-08-01 14:41 ` Jason A. Donenfeld
2022-08-11 0:17 ` Jason A. Donenfeld
2022-08-11 7:15 ` Sebastian Andrzej Siewior
2022-08-11 14:20 ` Jason A. Donenfeld
2022-08-15 10:26 ` David Laight
2022-08-16 14:02 ` Jason A. Donenfeld
2022-08-29 19:45 ` Sebastian Andrzej Siewior
2022-08-29 19:56 ` Jason A. Donenfeld
2022-08-30 10:13 ` Sebastian Andrzej Siewior
2022-08-30 15:24 ` Jason A. Donenfeld [this message]
2022-08-30 18:57 ` Sebastian Andrzej Siewior
2022-08-31 16:27 ` Jason A. Donenfeld
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=Yw4rsdA7xu4+UrLi@zx2c4.com \
--to=jason@zx2c4.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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