>From Sebastian Siewior <[EMAIL PROTECTED]> # This line is ignored. Subject: [RFC] padlock aes, unification of setkey()
Hello Herbert, I sit on those two since November. Back then Michal dropped me an email and told me that he will test it and get back to me. This didn't happen so far. The binary format of the key was the same, the last time I checked, so the second patch could really work :) One thing I'm concerned about is the stack utilization. The initial version had a structure with 256 bytes on the stack. Mine has a bigger structure with 484 bytes. I'm not sure if it is better to dynamically allocate it, move it to the private key structure or pad the generic aes structure in order to enforce the required alignment. Sebastian - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
