Brian Behlendorf aa9af22cdf Update all default taskq settings ... Over the years the default values for the taskqs used on Linux have differed slightly from illumos. In the vast majority of cases this was done to avoid creating an obnoxious number of idle threads which would pollute the process listing. With the addition of support for dynamic taskqs all multi-threaded queues should be created as dynamic taskqs. This allows us to get the best of both worlds. * The illumos default values for the I/O pipeline can be restored. These values are known to work well for most workloads. The only exception is the zio write interrupt taskq which is changed to ZTI_P(12, 8). At least under Linux more threads has been shown to improve performance, see commit 7e55f4e. * Reduces the number of idle threads on the system when it's not under heavy load. The maximum number of threads will only be created when they are required. * Remove the vdev_file_taskq and rely on the system_taskq instead which is now dynamic and may have up to 64-threads. Again this brings us back inline with upstream. * Tasks dispatched with taskq_dispatch_ent() are allowed to use dynamic taskqs. The Linux taskq implementation supports this. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Tim Chase <tim@chase2k.com> Closes #3507		2015-06-25 08:58:16 -07:00
..
Makefile.am	Illumos 5497 - lock contention on arcs_mtx	2015-06-11 10:27:25 -07:00
kernel.c	Illumos 5134 - if ZFS_DEBUG or debug= is set, libzpool should enable debug prints	2015-04-28 10:13:40 -07:00
taskq.c	Update all default taskq settings	2015-06-25 08:58:16 -07:00
util.c	Fix gcc cast warnings	2010-08-27 15:33:32 -07:00