Brian Behlendorf 044baf009a Use taskq for dump_bytes() ... The vn_rdwr() function performs I/O by calling the vfs_write() or vfs_read() functions. These functions reside just below the system call layer and the expectation is they have almost the entire 8k of stack space to work with. In fact, certain layered configurations such as ext+lvm+md+multipath require the majority of this stack to avoid stack overflows. To avoid this posibility the vn_rdwr() call in dump_bytes() has been moved to the ZIO_TYPE_FREE, taskq. This ensures that all I/O will be performed with the majority of the stack space available. This ends up being very similiar to as if the I/O were issued via sys_write() or sys_read(). Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #1399 Closes #1423		2013-05-06 14:05:42 -07:00
..
Makefile.am	Fix function relocations in libzpool	2013-02-05 15:33:32 -08:00
kernel.c	Silence 'old_umask' uninit variable warning	2013-05-01 17:05:58 -07:00
taskq.c	Use taskq for dump_bytes()	2013-05-06 14:05:42 -07:00
util.c	Fix gcc cast warnings	2010-08-27 15:33:32 -07:00