From: tytso@mit.edu (Theodore Ts'o)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH -next] random: Remove remaining relicts of rand_initialize_irq()
Date: Tue, 17 Jul 2012 17:42:19 -0400 [thread overview]
Message-ID: <20120717214219.GF6049@thunk.org> (raw)
In-Reply-To: <CACRpkdZe48FrDJx1p8ojfqwVBE95hSJipE8rViAi=E28uumYOQ@mail.gmail.com>
On Tue, Jul 17, 2012 at 08:57:19PM +0200, Linus Walleij wrote:
> So the IRQ will be auto-sampled now or something?
>
> Sorry for not quite following, which commit do I look at to
> understand this now...
Yes, there was a huge discussion on LKML about two weeks ago. The
key commit that will be going in during the next merge window is:
http://git.kernel.org/?p=linux/kernel/git/tytso/random.git;a=commitdiff;h=775f4b297b780601e61787b766f306ed3e1d23eb
There are a whole lot of other changes, of course, but that's the key
change which IRQF_SAMPLE_RANDOM a no-op. People have tested this
under extreme conditions (high speed networking tests with no
interrupt mitigations, etc.) and the patch as tweaked had no
measurable overhead, so we can simply sample every single commit with
a low-overhead fast path which uses per-cpu buffers, and then mix into
the /dev/random entropy pool less frequently (which is still fast, but
requires a few more memory accesses to shared memory that may incur
delays due to cache line bounces).
- Ted
next prev parent reply other threads:[~2012-07-17 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 11:33 [PATCH -next] random: Remove remaining relicts of rand_initialize_irq() Sedat Dilek
2012-07-17 17:12 ` Theodore Ts'o
2012-07-17 18:57 ` Linus Walleij
2012-07-17 21:42 ` Theodore Ts'o [this message]
2012-07-23 14:54 ` Linus Walleij
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=20120717214219.GF6049@thunk.org \
--to=tytso@mit.edu \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).