[PATCH 0/3] Various AIO retry related fixes and enhancements

[Suparna Bhattacharya]

The following patches are a collection of various (mostly 
retry infrastructure related) fixes, cleanups and enhancements
for AIO, that I have been maintaining for a while. I ran into
most of them while implementing support for default high
level retry methods (should also be helpful as a foundation
for some network AIO work). Now that we have in-tree use 
of the retry logic, it makes sense to merge these fixes 
upstream. They are mostly localised to AIO code.

Note: The latter two patches involve policy oriented 
optimizations to the AIO workqueue usage, so I chose 
to separate them out.

Please apply.

[1] aio-retry.patch
  Collection of AIO retry infrastructure fixes and enhancements
  AIO: Split iocb setup and execution in io_submit 
       (also fixes io_submit error reporting)
  AIO: Default high level retry methods
  AIO: Subtle use_mm/unuse_mm fix
  AIO: Code commenting
  AIO: Fix aio process hang on EINVAL (Daniel McNeil)
  AIO: flush workqueues before destroying ioctx'es 
  AIO: hold the context lock across unuse_mm
  AIO: Acquire task_lock in use_mm()
  AIO: Allow fops to override the retry method with their own
  AIO: Elevated ref count for AIO retries (Daniel McNeil)
  AIO: set_fs needed when calling use_mm
  AIO: flush workqueue on __put_ioctx (Chris Mason)
  AIO: Fix io_cancel to work with retries (Chris Mason)
  AIO: read-immediate option for socket/pipe retry support

[2] aio-splice-runlist.patch
  AIO: Splice runlist to be fairer across multiple io contexts

[3] aio-context-switch.patch
  AIO: Context switch reduction for retries (Chris Mason)
  AIO: Fix IO stalls with context switch reduction changes
	(Chris Mason)

Regards
Suparna

-- 
Suparna Bhattacharya (suparna@xxxxxxxxxx)
Linux Technology Center
IBM Software Lab, India

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/