[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081215033842.GA28499@gondor.apana.org.au>
Date: Mon, 15 Dec 2008 14:38:42 +1100
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Huang Ying <ying.huang@...el.com>,
Suresh Siddha <suresh.b.siddha@...el.com>
Cc: Sebastian Andrzej Siewior <linux-crypto@...breakpoint.cc>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"mingo@...e.hu" <mingo@...e.hu>,
"tglx@...utronix.de" <tglx@...utronix.de>
Subject: Re: [RFC PATCH crypto] AES: Add support to Intel AES-NI instructions
On Mon, Dec 15, 2008 at 10:19:02AM +0800, Huang Ying wrote:
>
> The general x86 implementation is used as the fall back for new AES-NI
> based implementation. Because AES-NI can not be used in kernel soft_irq
> context. If crypto layer is used to access general x86 implementation,
Why is that? The VIA PadLock also "touches" the SSE state but we still
use it on softirq paths.
In fact Suresh told me earlier that your AES instruction wasn't
going to have the SSE problems that VIA had, is this not the case?
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists