xfs: DIO writes within EOF don't need an ioend
authorDave Chinner <dchinner@redhat.com>
Thu, 16 Apr 2015 12:00:00 +0000 (22:00 +1000)
committerDave Chinner <david@fromorbit.com>
Thu, 16 Apr 2015 12:00:00 +0000 (22:00 +1000)
commita06c277a13c3620c8ee9304891758f2fcff9c4a4
tree4ab229dc91e9876a5a42df21f51b61c5977b7735
parent6dfa1b67e3b3a9bf536e2fb9ed99001c219822a5
xfs: DIO writes within EOF don't need an ioend

DIO writes that lie entirely within EOF have nothing to do in IO
completion. In this case, we don't need no steekin' ioend, and so we
can avoid allocating an ioend until we have a mapping that spans
EOF.

This means that IO completion has two contexts - deferred completion
to the dio workqueue that uses an ioend, and interrupt completion
that does nothing because there is nothing that can be done in this
context.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_aops.c
fs/xfs/xfs_trace.h
This page took 0.02453 seconds and 5 git commands to generate.