From: Rick Altherr <raltherr@google.com>
To: alex@digriz.org.uk
Cc: openbmc@lists.ozlabs.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Matt Mackall <mpm@selenic.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] hw_random: timeriomem_rng: Migrate to new API and improve performance
Date: Wed, 5 Apr 2017 16:20:57 -0700 [thread overview]
Message-ID: <20170405232100.2023-1-raltherr@google.com> (raw)
AST2400 can generate 32-bits of random data every 1us. Original driver
was limited to one 32-bit read every jiffie due to deprecated API and use
of timers. Migrating to new hwrng API and switching to hrtimers
improves read performance of /dev/hwrng to 13Mb/s.
Changes in v2:
- Split API migration into separate patch
- Split type and variable renames into separate patch
- Split performance improvements into separate patch
Rick Altherr (3):
hw_random: Migrate timeriomem_rng to new API
hw_random: timeriomem_rng: Shorten verbose type and variable names
hw_random: timeriomem_rng: Improve performance for sub-jiffie update
periods
drivers/char/hw_random/timeriomem-rng.c | 157 ++++++++++++++++----------------
1 file changed, 80 insertions(+), 77 deletions(-)
--
2.12.2.715.g7642488e1d-goog
next reply other threads:[~2017-04-05 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 23:20 Rick Altherr [this message]
2017-04-05 23:20 ` [PATCH v2 1/3] hw_random: Migrate timeriomem_rng to new API Rick Altherr
2017-04-05 23:20 ` [PATCH v2 2/3] hw_random: timeriomem_rng: Shorten verbose type and variable names Rick Altherr
2017-04-05 23:21 ` [PATCH v2 3/3] hw_random: timeriomem_rng: Improve performance for sub-jiffie update periods Rick Altherr
2017-04-10 11:22 ` [PATCH v2 0/3] hw_random: timeriomem_rng: Migrate to new API and improve performance Herbert Xu
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=20170405232100.2023-1-raltherr@google.com \
--to=raltherr@google.com \
--cc=alex@digriz.org.uk \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=openbmc@lists.ozlabs.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