Hi Herbert, On 01/13/2015 09:38 PM, Herbert Xu wrote: > What you want is AIO so we should try to use that interface rather > than creating some funky crypto-specific interface. > > Dave, the AIO hooks in net/socket.c is currently simply pointing > to the sync implementation. What are you thoughts on allowing > socket implementations to supply these hooks? > > The algif interface can then use these hooks to implement AIO > which is useful for maximising the hardware performance without > resorting to loads of threads. But then would you like to extend AIO interface to take the IV and something that would indicate the encrypt/decrypt operation on aio_write()? Also as far as I can see AIO doesn't support splice() operation for zero copy, which is the main thing here. >From the other hand it shouldn't be a problem to add crypto specific stuff to include/uapi/linux/if_alg.h, because it is all about crypto anyway, is it not? If you have a better way how to indicate that data processing should start on the last page in sendpage() instead of ALG_OP_IN_PLACE I would be happy to use it. Thanks, 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
