Change Details

The KTLS crypto callback always locks the session to deliver a wakeup. But if we're handling the operation synchonously this is wasted effort. On an Ampere server this results in a large amount of sleepqueue lock contention. Use CRYPTO_SESS_SYNC() to determine whether the operation will be completed asynchonously or not, and select a callback appropriately.

The KTLS crypto callback always locks the session to deliver a wakeup. But if we're handling the operation synchronously this is wasted effort. On an Ampere server this results in a large amount of sleepqueue lock contention. Use CRYPTO_SESS_SYNC() to determine whether the operation will be completed asynchronously or not, and select a callback appropriately.

The KTLS crypto callback always locks the session to deliver a wakeup. But if we're handling the operation synchronously this is wasted effort. On an Ampere server this results in a large amount of sleepqueue lock contention. Use CRYPTO_SESS_SYNC() to determine whether the operation will be completed asynchronously or not, and select a callback appropriately.