Pawel Jakub Dawidek 0c879bd990 Before this change when GELI detected hardware crypto acceleration it will ... start only one worker thread. For software crypto it will start by default N worker threads where N is the number of available CPUs. This is not optimal if hardware crypto is AES-NI, which uses CPU for AES calculations. Change that to always start one worker thread for every available CPU. Number of worker threads per GELI provider can be easly reduced with kern.geom.eli.threads sysctl/tunable and even for software crypto it should be reduced when using more providers. While here, when number of threads exceeds number of CPUs avilable don't reduce this number, assume the user knows what he is doing. Reported by: Yuri Karaban <dev@dev97.com> MFC after: 3 days		2011-10-27 16:12:25 +00:00
..
g_eli_crypto.c	Update copyright years.	2010-09-23 12:02:08 +00:00
g_eli_ctl.c	Version 6 is compatible with version 5 when it comes to control commands.	2011-05-08 09:25:54 +00:00
g_eli_integrity.c	When support for multiple encryption keys was committed, GELI integrity mode	2011-05-08 09:17:56 +00:00
g_eli_key_cache.c	Fix a memory leak possible in g_eli_key_allocate() if the key with the	2011-05-15 12:39:30 +00:00
g_eli_key.c	Instead of allocating memory for all the keys at device attach,	2011-04-21 13:31:43 +00:00
g_eli_privacy.c	Instead of allocating memory for all the keys at device attach,	2011-04-21 13:31:43 +00:00
g_eli.c	Before this change when GELI detected hardware crypto acceleration it will	2011-10-27 16:12:25 +00:00
g_eli.h	Before this change when GELI detected hardware crypto acceleration it will	2011-10-27 16:12:25 +00:00
pkcs5v2.c
pkcs5v2.h