From: Michael Buesch <mb@bu3sch.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Patrick McHardy <kaber@trash.net>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
linux-crypto@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC HIFN 00/02]: RNG support
Date: Sun, 18 Nov 2007 11:27:27 +0100 [thread overview]
Message-ID: <200711181127.28326.mb@bu3sch.de> (raw)
In-Reply-To: <20071118040401.GA25625@gondor.apana.org.au>
On Sunday 18 November 2007 05:04:01 Herbert Xu wrote:
> On Sun, Nov 18, 2007 at 04:30:40AM +0100, Patrick McHardy wrote:
> >
> > On a related issue, I think the rng interface is not very suitable
> > for chips like HIFN that have a constant random bandwidth, it would
> > make a lot more sense to return the time to wait to the core, instead
> > of waiting 10us in all cases. 256 cycles at a speed of 266MHz comes
> > down to 0.96us, so we're waiting about 10 times as long as necessary.
> > Since its busy waiting anyway, I'd think that from a performance POV
> > constant polling or returning the exact amount of time would be more
> > reasonable.
>
> I agree, a better interface would be to let the hardware do the
> blocking where necessary.
>
> Michael, what do you think about this?
Patches are welcome. ;)
--
Greetings Michael.
prev parent reply other threads:[~2007-11-18 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071117192949.19399.75523.sendpatchset@localhost.localdomain>
[not found] ` <20071117195324.GA4010@2ka.mipt.ru>
[not found] ` <20071118031402.GA25388@gondor.apana.org.au>
[not found] ` <473FB1E0.600@trash.net>
2007-11-18 4:04 ` [RFC HIFN 00/02]: RNG support Herbert Xu
2007-11-18 4:04 ` Herbert Xu
2007-11-18 10:27 ` Michael Buesch [this message]
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=200711181127.28326.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--cc=kaber@trash.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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