diff options
author | Christoph Hellwig <hch@lst.de> | 2010-06-17 08:54:16 +0200 |
---|---|---|
committer | Jens Axboe <jaxboe@fusionio.com> | 2010-08-07 18:15:44 +0200 |
commit | 41f2df62894bfcd3bf868af916b32b90aa7168dc (patch) | |
tree | b582399975cd1cf19aa8b6e67623f252b7cada85 /drivers/scsi/aha1542.c | |
parent | 01b6b67edabe864391163dc6405e2cb454f108db (diff) | |
download | op-kernel-dev-41f2df62894bfcd3bf868af916b32b90aa7168dc.zip op-kernel-dev-41f2df62894bfcd3bf868af916b32b90aa7168dc.tar.gz |
block: BARRIER request should imply SYNC
A barrier request should by defintion have priority in get_request
and let the queue be unplugged immediately as it's blocking all forward
progress due to the queue draining.
Most filesystems already get this implicitly by the way how submit_bh
treats the buffer_ordered flag, and gfs2 sets it explicitly. But btrfs
and XFS are still forgetting to set the flag, as is blkdev_issue_flush
and some places in DM/MD.
For XFS on metadata heavy workloads this gives a consistent speedup
in the 2-3% range.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'drivers/scsi/aha1542.c')
0 files changed, 0 insertions, 0 deletions