dm verity: switch to using asynchronous hash crypto API
authorGilad Ben-Yossef <gilad@benyossef.com>
Sun, 19 Feb 2017 12:46:07 +0000 (14:46 +0200)
committerMike Snitzer <snitzer@redhat.com>
Mon, 24 Apr 2017 19:37:04 +0000 (15:37 -0400)
commitd1ac3ff008fb9a48f91fc15920b4c8db24c0f03e
tree564a6181d22925a9dfc25eb7c69af735a0f6c399
parenta1b89132dc4f61071bdeaab92ea958e0953380a1
dm verity: switch to using asynchronous hash crypto API

Use of the synchronous digest API limits dm-verity to using pure
CPU based algorithm providers and rules out the use of off CPU
algorithm providers which are normally asynchronous by nature,
potentially freeing CPU cycles.

This can reduce performance per Watt in situations such as during
boot time when a lot of concurrent file accesses are made to the
protected volume.

Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
CC: Eric Biggers <ebiggers3@gmail.com>
CC: Ondrej Mosnáček <omosnacek+linux-crypto@gmail.com>
Tested-by: Milan Broz <gmazyland@gmail.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
drivers/md/dm-verity-fec.c
drivers/md/dm-verity-target.c
drivers/md/dm-verity.h