From: Stefan Hellermann <stefan@the2masters.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>,
linux-crypto@vger.kernel.org
Subject: Re: [RFC] [crypto] padlock-aes loadkey ondemand
Date: Wed, 02 Apr 2008 17:48:33 +0200 [thread overview]
Message-ID: <47F3AAD1.90406@the2masters.de> (raw)
In-Reply-To: <20080402065015.GA7421@gondor.apana.org.au>
Herbert Xu schrieb:
> On Wed, Apr 02, 2008 at 08:44:19AM +0200, Sebastian Siewior wrote:
>> Herbert: I was going to Cc you and ask if the speed improvements are
>> okey / enough to consider this patch for inclusion but I see now that
>> you found this thread on your own :) Do you want me to form a patch?
>
> Yes please! BTW, can VIA do SMP? If so then we'll need some code
> to deal with that and if not, we should add a run-time check to
> fail the module insertion if ever such a beast should arise.
Till now VIA has no SMP and nothing planed (as far as I know, I'm not a VIA guy). There
next gen processors will be called isaiah, without smp but with 64bit and lots of other
features ( http://www.via.com.tw/en/products/processors/isaiah-arch/ )
Cheers
Stefan
>
> Cheers,
next prev parent reply other threads:[~2008-04-02 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 22:33 [RFC] [crypto] padlock-aes loadkey ondemand Sebastian Siewior
2008-03-30 19:03 ` Stefan Hellermann
2008-03-30 21:01 ` Sebastian Siewior
2008-04-01 18:38 ` Stefan Hellermann
2008-04-02 6:44 ` Sebastian Siewior
2008-04-02 6:50 ` Herbert Xu
2008-04-02 7:17 ` Sebastian Siewior
2008-04-02 7:22 ` Herbert Xu
2008-08-07 14:53 ` Herbert Xu
2008-08-09 11:20 ` Sebastian Siewior
2008-08-31 6:01 ` Herbert Xu
2008-04-02 15:48 ` Stefan Hellermann [this message]
2008-04-09 16:38 ` Herbert Xu
2008-04-02 6:03 ` Herbert Xu
2008-04-02 6:26 ` Sebastian Siewior
2008-04-02 6:31 ` 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=47F3AAD1.90406@the2masters.de \
--to=stefan@the2masters.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.