dm crypt: use unbound workqueue for request processing
authorMikulas Patocka <mpatocka@redhat.com>
Fri, 13 Feb 2015 13:23:09 +0000 (08:23 -0500)
committerMike Snitzer <snitzer@redhat.com>
Mon, 16 Feb 2015 16:10:59 +0000 (11:10 -0500)
Use unbound workqueue by default so that work is automatically balanced
between available CPUs.  The original behavior of encrypting using the
same cpu that IO was submitted on can still be enabled by setting the
optional 'same_cpu_crypt' table argument.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>

No differences found