xfs: don't allocate an ioend for direct I/O completions
authorChristoph Hellwig <hch@lst.de>
Sun, 1 Feb 2015 23:02:09 +0000 (10:02 +1100)
committerDave Chinner <david@fromorbit.com>
Sun, 1 Feb 2015 23:02:09 +0000 (10:02 +1100)
commit2ba66237029d1ad6c1a5e2241b0ffbbfff55f750
tree7c85d7aec5513c39b8037100bea2b023f1dc9e53
parentf3d215526e6955028dfbbfd446db8716275fb0c7
xfs: don't allocate an ioend for direct I/O completions

Back in the days when the direct I/O ->end_io callback could be called
from interrupt context for AIO we needed a structure to hand off to the
workqueue, and reused the ioend structure for this purpose.  These days
->end_io is always called from user or workqueue context, which allows us
to avoid this memory allocation and simplify the code significantly.

[dchinner: removed now unused xfs_finish_ioend_sync() function after
   Brian Foster did an initial review. ]

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_aops.c
fs/xfs/xfs_aops.h