On Thu, Aug 11, 2011 at 10:50:49AM -0400, Andy Lutomirski wrote: > >> This is pretty similar to the situation with the Intel AES code. >> Over there they solved it by using the asynchronous interface and >> deferring the processing to a work queue. > > I have vague plans to clean up extended state handling and make > kernel_fpu_begin work efficiently from any context. (i.e. the first > kernel_fpu_begin after a context switch could take up to ~60 ns on Sandy > Bridge, but further calls to kernel_fpu_begin would be a single branch.) This is all well and good but you still need to deal with the case of !irq_fpu_usable. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> 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-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
