Searched hist:c972fa123c73501b4b0c6de7873754ea3205a5eb (Results 1 – 8 of 8) sorted by relevance
| /openbmc/qemu/crypto/ |
| H A D | block-qcow.c | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| H A D | blockpriv.h | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| H A D | block.c | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| H A D | block-luks.c | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| /openbmc/qemu/include/crypto/ |
| H A D | block.h | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| /openbmc/qemu/block/ |
| H A D | crypto.c | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| H A D | qcow.c | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
| H A D | qcow2.c | diff c972fa123c73501b4b0c6de7873754ea3205a5eb Fri Dec 07 10:13:51 CST 2018 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> crypto: support multiple threads accessing one QCryptoBlock
The two thing that should be handled are cipher and ivgen. For ivgen
the solution is just mutex, as iv calculations should not be long in
comparison with encryption/decryption. And for cipher let's just keep
per-thread ciphers.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|