freebsd-skq/sys/geom/eli
Alan Somers 6f818c1fb0 geli: enable direct dispatch
geli does all of its crypto operations in a separate thread pool, so
g_eli_start, g_eli_read_done, and g_eli_write_done don't actually do very
much work. Enabling direct dispatch eliminates the g_up/g_down bottlenecks,
doubling IOPs on my system. This change does not affect the thread pool.

Reviewed by:	markj
MFC after:	2 weeks
Sponsored by:	Axcient
Differential Revision:	https://reviews.freebsd.org/D25587
2020-07-08 17:12:12 +00:00
..
g_eli_crypto.c Add support for optional separate output buffers to in-kernel crypto. 2020-05-25 22:12:04 +00:00
g_eli_ctl.c Use zfree() instead of explicit_bzero() and free(). 2020-06-25 20:17:34 +00:00
g_eli_hmac.c geli: style nits 2019-06-12 19:29:48 +00:00
g_eli_integrity.c Add support for optional separate output buffers to in-kernel crypto. 2020-05-25 22:12:04 +00:00
g_eli_key_cache.c Use zfree() instead of explicit_bzero() and free(). 2020-06-25 20:17:34 +00:00
g_eli_key.c Introduce the 'n' flag for the geli attach command. 2018-05-09 20:53:38 +00:00
g_eli_privacy.c Add support for optional separate output buffers to in-kernel crypto. 2020-05-25 22:12:04 +00:00
g_eli.c geli: enable direct dispatch 2020-07-08 17:12:12 +00:00
g_eli.h Add a crypto capability flag for accelerated software drivers. 2020-06-09 22:26:07 +00:00
pkcs5v2.c geli: partially revert r348709 2019-06-12 19:29:12 +00:00
pkcs5v2.h geli: partially revert r348709 2019-06-12 19:29:12 +00:00