mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Yu Kuai <yukuai@fnnas.com>
Cc: hch@infradead.org, song@kernel.org, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org, linan122@huawei.com
Subject: Re: [PATCH] md/raid5: set chunk_sectors to enable full stripe I/O splitting
Date: Mon, 23 Feb 2026 08:26:33 +0100	[thread overview]
Message-ID: <a48b64d7-e40f-49e3-a118-b27723b09c39@molgen.mpg.de> (raw)
In-Reply-To: <20260223035834.3132498-1-yukuai@fnnas.com>

Dear Kuai,


Thank you for your patch.

Am 23.02.26 um 04:58 schrieb Yu Kuai:
> Set chunk_sectors to the full stripe width (io_opt) so that the block
> layer splits I/O at full stripe boundaries. This ensures that large
> writes are aligned to full stripes, avoiding the read-modify-write
> overhead that occurs with partial stripe writes in RAID-5/6.
> 
> When chunk_sectors is set, the block layer's bio splitting logic in
> get_max_io_size() uses blk_boundary_sectors_left() to limit I/O size
> to the boundary. This naturally aligns split bios to full stripe
> boundaries, enabling more efficient full stripe writes.
> 
> Test results with 24-disk RAID5 (chunk_size=64k):
>    dd if=/dev/zero of=/dev/md0 bs=10M oflag=direct
>    Before: 461 MB/s
>    After:  520 MB/s  (+12.8%)

Sweet.

> Suggested-by: Christoph Hellwig <hch@infradead.org>
> Signed-off-by: Yu Kuai <yukuai@fnnas.com>

Once committed, should this be backported to the longterm and stable series?

> ---
>   drivers/md/raid5.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 8854e024f311..810d936560d1 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -7783,6 +7783,7 @@ static int raid5_set_limits(struct mddev *mddev)
>   	lim.logical_block_size = mddev->logical_block_size;
>   	lim.io_min = mddev->chunk_sectors << 9;
>   	lim.io_opt = lim.io_min * (conf->raid_disks - conf->max_degraded);
> +	lim.chunk_sectors = lim.io_opt >> 9;
>   	lim.features |= BLK_FEAT_RAID_PARTIAL_STRIPES_EXPENSIVE;
>   	lim.discard_granularity = stripe;
>   	lim.max_write_zeroes_sectors = 0;

Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>


Kind regards,

Paul

  reply	other threads:[~2026-02-23  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  3:58 Yu Kuai
2026-02-23  7:26 ` Paul Menzel [this message]
2026-03-04  2:36   ` Yu Kuai
2026-02-23 14:05 ` Christoph Hellwig
2026-03-04  2:36 ` Yu Kuai

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=a48b64d7-e40f-49e3-a118-b27723b09c39@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=hch@infradead.org \
    --cc=linan122@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yukuai@fnnas.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

all inboxes | Powered by JetHome®