Sorry, I did not realize the case when I created the commit. However, although I don't understand its scenario, in my opinion, adding one redundant argument for all sockets to satisfy the special case seems unreasonable for us. Regards, Ying On 03/11/2015 10:37 AM, Tadeusz Struk wrote: > Hi, > After couple of attempts to implement an user space interface to crypto HW that would meet our performance requirements, and after discussion with Herbert, we have come to conclusion that using AF_ALG sockets and AIO interface is the way to go. > Unfortunately it looks like AIO operations will no longer be supported on sockets because of the commit 1b784140474e4fc94281a49e96c67d29df0efbde. > My question is why do we want to abandon AIO support in the socket layer? Is it not worth keeping it for scenarios like this? > Do we have any alternative? > The mentioned patch attached for your reference. > Regards, > Tadeusz > -- 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
