Originally posted by willmore
View Post
Edit: I think we just read it differently. From what I got out of it, they modified both the dm-crypt AND Crypto API code to remove queuing and make everything synchronous, although they left a threading/queuing toggle in their dm-crypt modifications. But it seems like in the vast majority of the time, their modified code uses synchronous cipher implementations whenever possible.
I was wondering about the opposite case. Leave Crypto API async, but remove the queuing from dm-crypt. I didn't see any numbers where they left Crypto API async, but modified dm-crypt to remove its queuing..
Leave a comment: