Mike Snitzer ed8b752bcc dm table: set flush capability based on underlying devices
DM has always advertised both REQ_FLUSH and REQ_FUA flush capabilities
regardless of whether or not a given DM device's underlying devices
also advertised a need for them.

Block's flush-merge changes from 2.6.39 have proven to be more costly
for DM devices.  Performance regressions have been reported even when
DM's underlying devices do not advertise that they have a write cache.

Fix the performance regressions by configuring a DM device's flushing
capabilities based on those of the underlying devices' capabilities.

Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2011-08-02 12:32:08 +01:00
..
2011-07-27 11:00:37 +10:00
2011-07-27 11:00:37 +10:00
2011-08-02 12:32:01 +01:00
2010-08-12 04:14:11 +01:00
2011-08-02 12:32:02 +01:00
2011-07-26 16:49:47 -07:00
2011-08-02 12:32:07 +01:00
2011-03-31 11:26:23 -03:00
2011-03-24 13:54:35 +00:00
2007-10-20 02:01:26 +01:00
2010-08-12 04:14:12 +01:00
2011-03-31 11:26:23 -03:00
2011-08-02 12:32:07 +01:00
2011-03-24 13:54:24 +00:00