On 09/06/2025 16:19, Mikulas Patocka wrote:
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index 24a857ff6d0b..4f1f7173740c 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -430,6 +430,10 @@ static int dm_set_device_limits(struct dm_target *ti,
struct dm_dev *dev,
On 06/06/2025 16:16, Nilay Shroff wrote:
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index 24a857ff6d0b..4f1f7173740c 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -430,6 +430,10 @@ static int dm_set_device_limits(struct dm_target *ti,
struct dm_dev *dev,
On Thu, 5 Jun 2025, John Garry wrote:
> Currently we use min io size as the chunk size when deciding on the limit
> of atomic write size.
>
> Using min io size is not reliable, as this may be mutated when stacking
> the bottom device limits.
>
> The block stacking limits will rely on chunk_se
On 6/5/25 8:38 PM, John Garry wrote:
> Currently we use min io size as the chunk size when deciding on the limit
> of atomic write size.
>
> Using min io size is not reliable, as this may be mutated when stacking
> the bottom device limits.
>
> The block stacking limits will rely on chunk_sect
Currently we use min io size as the chunk size when deciding on the limit
of atomic write size.
Using min io size is not reliable, as this may be mutated when stacking
the bottom device limits.
The block stacking limits will rely on chunk_sectors in future, so set
this value (to the chunk size).
