On 01/11/2012 01:00 AM, Alexey Dobriyan wrote: > commit f9e2bca6c22d75a289a349f869701214d63b5060 > aka "crypto: sha512 - Move message schedule W[80] to static percpu area" > created global message schedule area. [snip] > I personally don't understand this changelog entry: > > "The message schedule W (u64[80]) is too big for the stack." > > Hash context is dynamically allocated. My original patch did the same thing as yours and put the message schedule on the stack in sha512_transform. Herbert argued [1], that it was too big and suggested to store it in a static per-cpu area. [1] - http://www.mail-archive.com/linux-crypto@xxxxxxxxxxxxxxx/msg02527.html -- 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
