public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Ondřej Bílka" <neleai@seznam.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] AES instead of SHA1 for /dev/urandom
Date: Wed, 12 Dec 2012 13:08:26 +1100	[thread overview]
Message-ID: <20121212130826.7940b428@notabene.brown> (raw)
In-Reply-To: <20121212020354.GA30879@domone.kolej.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

On Wed, 12 Dec 2012 03:03:54 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:

> I consider to speed-up /dev/urandom on recent intel processors by
> using hardware aes. Same for accelerated aes crypto.
> 
> Would you accept a patch if I wrote it?

Have you read  https://lwn.net/Articles/525459  ?

In particular the paragraph containing:

   A member of the audience asked why the kernel couldn't just do away with
   the existing system and use the HWRNG directly.

Does that answer your question in any way?

NeilBrown


> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-12-12  2:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  2:03 [RFC] AES instead of SHA1 for /dev/urandom Ondřej Bílka
2012-12-12  2:08 ` NeilBrown [this message]
2012-12-12  8:58   ` Ondřej Bílka
2012-12-12  9:10     ` NeilBrown
2013-01-01 22:50       ` Pavel Machek

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=20121212130826.7940b428@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neleai@seznam.cz \
    /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