From: Mikulas Patocka <mpatocka@redhat.com>
To: John Garry <john.g.garry@oracle.com>
Cc: agk@redhat.com, snitzer@kernel.org, song@kernel.org,
yukuai3@huawei.com, hch@lst.de, nilay@linux.ibm.com,
axboe@kernel.dk, dm-devel@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-block@vger.kernel.org, ojaswin@linux.ibm.com,
martin.petersen@oracle.com
Subject: Re: [PATCH RFC 3/4] dm-stripe: limit chunk_sectors to the stripe size
Date: Mon, 9 Jun 2025 17:19:51 +0200 (CEST) [thread overview]
Message-ID: <e7e147a8-f22e-e420-1497-5b31be9ab4e3@redhat.com> (raw)
In-Reply-To: <20250605150857.4061971-4-john.g.garry@oracle.com>
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_sectors in future, so set
> this value (to the chunk size).
>
> Introduce a flag - DM_TARGET_STRIPED - and check this in
> dm_set_device_limits() when setting this limit.
>
> Signed-off-by: John Garry <john.g.garry@oracle.com>
> ---
> drivers/md/dm-stripe.c | 3 ++-
> drivers/md/dm-table.c | 4 ++++
> include/linux/device-mapper.h | 3 +++
> 3 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/md/dm-stripe.c b/drivers/md/dm-stripe.c
> index a7dc04bd55e5..c30df6715149 100644
> --- a/drivers/md/dm-stripe.c
> +++ b/drivers/md/dm-stripe.c
> @@ -466,7 +466,8 @@ static struct target_type stripe_target = {
> .name = "striped",
> .version = {1, 7, 0},
> .features = DM_TARGET_PASSES_INTEGRITY | DM_TARGET_NOWAIT |
> - DM_TARGET_ATOMIC_WRITES | DM_TARGET_PASSES_CRYPTO,
> + DM_TARGET_ATOMIC_WRITES | DM_TARGET_PASSES_CRYPTO |
> + DM_TARGET_STRIPED,
> .module = THIS_MODULE,
> .ctr = stripe_ctr,
> .dtr = stripe_dtr,
> 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,
> return 0;
> }
>
> + /* For striped types, limit the chunk_sectors to the chunk size */
> + if (dm_target_supports_striped(ti->type))
> + limits->chunk_sectors = len >> SECTOR_SHIFT;
> +
len is already in sectors, so why do we shift it right?
Could this logic be moved to the function stripe_io_hints, so that we
don't have to add a new flag for that and that we don't have to modify the
generic dm code?
Mikulas
> mutex_lock(&q->limits_lock);
> /*
> * BLK_FEAT_ATOMIC_WRITES is not inherited from the bottom device in
> diff --git a/include/linux/device-mapper.h b/include/linux/device-mapper.h
> index cb95951547ab..a863523b69ee 100644
> --- a/include/linux/device-mapper.h
> +++ b/include/linux/device-mapper.h
> @@ -309,6 +309,9 @@ struct target_type {
> #define DM_TARGET_ATOMIC_WRITES 0x00000400
> #define dm_target_supports_atomic_writes(type) ((type)->features & DM_TARGET_ATOMIC_WRITES)
>
> +#define DM_TARGET_STRIPED 0x00000800
> +#define dm_target_supports_striped(type) ((type)->features & DM_TARGET_STRIPED)
> +
> struct dm_target {
> struct dm_table *table;
> struct target_type *type;
> --
> 2.31.1
>
next prev parent reply other threads:[~2025-06-09 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 15:08 [PATCH RFC 0/4] block: set chunk_sectors from stacked dev stripe size John Garry
2025-06-05 15:08 ` [PATCH RFC 1/4] md/raid0: set chunk_sectors limit John Garry
2025-06-05 15:08 ` [PATCH RFC 2/4] md/raid10: " John Garry
2025-06-05 15:08 ` [PATCH RFC 3/4] dm-stripe: limit chunk_sectors to the stripe size John Garry
2025-06-06 15:16 ` Nilay Shroff
2025-06-12 10:01 ` John Garry
2025-06-09 15:19 ` Mikulas Patocka [this message]
2025-06-12 9:15 ` John Garry
2025-06-05 15:08 ` [PATCH RFC 4/4] block: use chunk_sectors when evaluating stacked atomic write limits John Garry
2025-06-06 15:23 ` Nilay Shroff
2025-06-12 9:17 ` John Garry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7e147a8-f22e-e420-1497-5b31be9ab4e3@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nilay@linux.ibm.com \
--cc=ojaswin@linux.ibm.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).