diff options
author | Brian Behlendorf <[email protected]> | 2014-06-10 14:37:13 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2014-06-11 16:32:57 -0700 |
commit | 7f6884f419f822f89609f6ed7595f78d12c31834 (patch) | |
tree | 0321e9dbb89dee96b51621f1e774dd6d59737d29 /module/zfs | |
parent | 0f629346bb335d8521600ae1491884fe8a8a2d27 (diff) |
Revert "Fix __zio_execute() asynchronous dispatch"
This reverts commit 91579709fccd3e55a21970742b66c388fb1403db which
limited the asynchronous dispatch to kernel space. We want to do
this for two reasons:
1) While we have slightly more headroom in user space excessively
deep stacks have been observed while running ztest, see #2293.
2) Removing this conditional makes the pipeline behave consistently
regardless of if it's executing in kernel space or user space.
This way we're more likely to uncover subtle issues with ztest.
Signed-off-by: Richard Yao <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #2384
Diffstat (limited to 'module/zfs')
-rw-r--r-- | module/zfs/zio.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/module/zfs/zio.c b/module/zfs/zio.c index 26c498979..332d50c69 100644 --- a/module/zfs/zio.c +++ b/module/zfs/zio.c @@ -1342,7 +1342,6 @@ __zio_execute(zio_t *zio) return; } -#ifdef _KERNEL /* * If we executing in the context of the tx_sync_thread, * or we are performing pool initialization outside of a @@ -1357,7 +1356,6 @@ __zio_execute(zio_t *zio) zio_taskq_dispatch(zio, ZIO_TASKQ_ISSUE, cut); return; } -#endif zio->io_stage = stage; rv = zio_pipeline[highbit(stage) - 1](zio); |