From: Wes Malone <wes@mitsi.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] rng-tools: disable libjitterentropy due to cpu usage
Date: Mon, 2 May 2022 16:10:00 -0500 [thread overview]
Message-ID: <20220502211001.4183095-1-wes@mitsi.com> (raw)
Since updating to kirkstone from hardknott, after boot rngd maxes out my
rpi4's processor for minutes initializing JITTER. The sustained CPU
usage was triggering my resource monitoring alerts. Changing config to
disable jitter with -x jitter stops the initialization process and uses
just the pi's hardware rng source. Since that solved the problem I
disabled building rng-tools with libjitterentropy enabled.
I submitted the change to meta-raspberrypi (pull #1057) where kraj noted
that the CPU spike is seen even on qemu so the change should go in the
core layer.
next reply other threads:[~2022-05-02 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:10 Wes Malone [this message]
2022-05-02 21:10 ` [PATCH] rng-tools: disable libjitterentropy due to cpu usage Wes Malone
2022-05-02 21:33 ` [OE-core] " William Kennington
2022-05-03 4:46 ` Alexander Kanavin
2022-05-03 15:22 ` Wes Malone
2022-05-03 16:21 ` Khem Raj
2022-05-05 21:34 ` Wes Malone
2022-05-05 22:50 ` Khem Raj
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=20220502211001.4183095-1-wes@mitsi.com \
--to=wes@mitsi.com \
--cc=openembedded-core@lists.openembedded.org \
/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