Tim Chase d33931a83a Write issue taskq shouldn't be dynamic ... This is as much an upstream compatibility as it's a bit of a performance gain. The illumos taskq implemention doesn't allow a TASKQ_THREADS_CPU_PCT type to be dynamic and in fact enforces as much with an ASSERT. As to performance, if this taskq is dynamic, it can cause excessive contention on tq_lock as the threads are created and destroyed because it can see bursts of many thousands of tasks in a short time, particularly in heavy high-concurrency zvol write workloads. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Tim Chase <tim@chase2k.com> Closes #5236		2016-10-10 15:19:14 -07:00
..
avl	Fix uninitialized variable in avl_add()	2016-07-25 14:21:34 -07:00
icp	Porting over some ICP code that was missed in #4760	2016-10-10 11:34:57 -07:00
nvpair	Fix file permissions	2016-10-08 14:57:56 -07:00
unicode	Build user-space with different gcc optimization levels	2016-08-09 14:40:35 -07:00
zcommon	Fletcher4: Incremental updates and ctx calculation	2016-10-07 12:44:12 -07:00
zfs	Write issue taskq shouldn't be dynamic	2016-10-10 15:19:14 -07:00
zpios	kmem_zalloc with KM_SLEEP will never return NULL	2016-09-01 11:39:45 -07:00
.gitignore	module/.gitignore: Add *.dwo (#4580)	2016-05-02 09:07:04 -07:00
Makefile.in	Illumos Crypto Port module added to enable native encryption in zfs	2016-07-20 10:43:30 -07:00