linux-toradex.git/drivers/md/dm-table.c, branch v3.2.28

dm table: add immutable feature

2011-10-31T20:19:04+00:00

Introduce DM_TARGET_IMMUTABLE to indicate that the target type cannot be mixed
with any other target type, and once loaded into a device, it cannot be
replaced with a table containing a different type.

The thin provisioning pool device will use this.

Signed-off-by: Alasdair G Kergon

dm table: add always writeable feature

2011-10-31T20:19:02+00:00

Add a target feature flag DM_TARGET_ALWAYS_WRITEABLE to indicate that a target
does not support read-only mode.

The initial implementation of the thin provisioning target uses this.

Signed-off-by: Alasdair G Kergon

dm table: add singleton feature

2011-10-31T20:19:00+00:00

Introduce the concept of a singleton table which contains exactly one target.

If a target type sets the DM_TARGET_SINGLETON feature bit device-mapper
will ensure that any table that includes that target contains no others.

The thin provisioning pool target uses this.

Signed-off-by: Alasdair G Kergon

dm table: propagate non rotational flag

2011-10-31T20:18:50+00:00

Allow QUEUE_FLAG_NONROT to propagate up the device stack if all
underlying devices are non-rotational.  Tools like ureadahead will
schedule IOs differently based on the rotational flag.

With this patch, I see boot time go from 7.75 s to 7.46 s on my device.

Suggested-by: J. Richard Barnette 
Signed-off-by: Mandeep Singh Baines 
Signed-off-by: Mike Snitzer 
Cc: Neil Brown 
Cc: Jens Axboe 
Cc: Martin K. Petersen 
Cc: dm-devel@redhat.com
Signed-off-by: Alasdair G Kergon

dm crypt: always disable discard_zeroes_data

2011-09-25T22:26:21+00:00

If optional discard support in dm-crypt is enabled, discards requests
bypass the crypt queue and blocks of the underlying device are discarded.
For the read path, discarded blocks are handled the same as normal
ciphertext blocks, thus decrypted.

So if the underlying device announces discarded regions return zeroes,
dm-crypt must disable this flag because after decryption there is just
random noise instead of zeroes.

Signed-off-by: Milan Broz 
Signed-off-by: Alasdair G Kergon

dm table: avoid crash if integrity profile changes

2011-09-25T22:26:17+00:00

Commit a63a5cf (dm: improve block integrity support) introduced a
two-phase initialization of a DM device's integrity profile.  This
patch avoids dereferencing a NULL 'template_disk' pointer in
blk_integrity_register() if there is an integrity profile mismatch in
dm_table_set_integrity().

This can occur if the integrity profiles for stacked devices in a DM
table are changed between the call to dm_table_prealloc_integrity() and
dm_table_set_integrity().

Reported-by: Zdenek Kabelac 
Signed-off-by: Mike Snitzer 
Signed-off-by: Alasdair G Kergon 
Cc: stable@kernel.org # 2.6.39

dm table: set flush capability based on underlying devices

2011-08-02T11:32:08+00:00

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 
Signed-off-by: Alasdair G Kergon

dm table: share target argument parsing functions

2011-08-02T11:32:04+00:00

Move multipath target argument parsing code into dm-table so other
targets can share it.

Signed-off-by: Mike Snitzer 
Signed-off-by: Alasdair G Kergon

dm: ignore merge_bvec for snapshots when safe

2011-08-02T11:32:04+00:00

Add a new flag DMF_MERGE_IS_OPTIONAL to struct mapped_device to indicate
whether the device can accept bios larger than the size its merge
function returns.  When set, use this to send large bios to snapshots
which can split them if necessary.  Snapshot I/O may be significantly
fragmented and this approach seems to improve peformance.

Before the patch, dm_set_device_limits restricted bio size to page size
if the underlying device had a merge function and the target didn't
provide a merge function.  After the patch, dm_set_device_limits
restricts bio size to page size if the underlying device has a merge
function, doesn't have DMF_MERGE_IS_OPTIONAL flag and the target doesn't
provide a merge function.

The snapshot target can't provide a merge function because when the merge
function is called, it is impossible to determine where the bio will be
remapped.  Previously this led us to impose a 4k limit, which we can
now remove if the snapshot store is located on a device without a merge
function.  Together with another patch for optimizing full chunk writes,
it improves performance from 29MB/s to 40MB/s when writing to the
filesystem on snapshot store.

If the snapshot store is placed on a non-dm device with a merge function
(such as md-raid), device mapper still limits all bios to page size.

Signed-off-by: Mikulas Patocka 
Signed-off-by: Alasdair G Kergon

dm table: clean dm_get_device and move exports

2011-08-02T11:32:04+00:00

There is no need for __table_get_device to be factored out.
Also move the exports to the end of their respective functions.

Signed-off-by: Mike Snitzer 
Signed-off-by: Alasdair G Kergon