From: John Garry <john.g.garry@oracle.com>
To: axboe@kernel.dk, song@kernel.org, yukuai3@huawei.com, hch@lst.de
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, martin.petersen@oracle.com
Subject: Re: [PATCH v4 0/5] RAID 0/1/10 atomic write support
Date: Thu, 14 Nov 2024 08:22:26 +0000 [thread overview]
Message-ID: <8b3c057b-123c-4e57-9221-447ff1b073a6@oracle.com> (raw)
In-Reply-To: <20241112124256.4106435-1-john.g.garry@oracle.com>
On 12/11/2024 12:42, John Garry wrote:
Hi Song, Kuai,
Can you check the remaining 2x patches in this series when you get a chance?
I was hoping that I could get this queued for 6.13 via the block tree.
Thanks,
John
Ps. I do appreciate that I am pinging on this quite early, but those
patches mentioned have not changed since the last revision.
> This series introduces atomic write support for software RAID 0/1/10.
>
> The main changes are to ensure that we can calculate the stacked device
> request_queue limits appropriately for atomic writes. Fundamentally, if
> some bottom does not support atomic writes, then atomic writes are not
> supported for the top device. Furthermore, the atomic writes limits are
> the lowest common supported limits from all bottom devices.
>
> Flag BLK_FEAT_ATOMIC_WRITES_STACKED is introduced to enable atomic writes
> for stacked devices selectively. This ensures that we can analyze and test
> atomic writes support per individual md/dm personality (prior to
> enabling).
>
> Based on 0b4ace9da58d (for-6.13/block) nvme-multipath: don't bother
> clearing max_hw_zone_append_sectors
>
> Differences to v3:
> - Add RB tags from Christoph and Kuai (thanks!)
> - Rebase
>
> Differences to v2:
> - Refactor blk_stack_atomic_writes_limits() (Christoph)
> - Relocate RAID 1/10 BB check (Kuai)
> - Add RB tag from Christoph (Thanks!)
> - Set REQ_ATOMIC for RAID 1/10
>
> John Garry (5):
> block: Add extra checks in blk_validate_atomic_write_limits()
> block: Support atomic writes limits for stacked devices
> md/raid0: Atomic write support
> md/raid1: Atomic write support
> md/raid10: Atomic write support
>
> block/blk-settings.c | 132 +++++++++++++++++++++++++++++++++++++++++
> drivers/md/raid0.c | 1 +
> drivers/md/raid1.c | 14 ++++-
> drivers/md/raid10.c | 14 ++++-
> include/linux/blkdev.h | 4 ++
> 5 files changed, 161 insertions(+), 4 deletions(-)
>
prev parent reply other threads:[~2024-11-14 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 12:42 John Garry
2024-11-12 12:42 ` [PATCH v4 1/5] block: Add extra checks in blk_validate_atomic_write_limits() John Garry
2024-11-12 12:42 ` [PATCH v4 2/5] block: Support atomic writes limits for stacked devices John Garry
2024-11-12 12:42 ` [PATCH v4 3/5] md/raid0: Atomic write support John Garry
2024-11-12 12:42 ` [PATCH v4 4/5] md/raid1: " John Garry
2024-11-16 3:51 ` Yu Kuai
2024-11-12 12:42 ` [PATCH v4 5/5] md/raid10: " John Garry
2024-11-15 18:19 ` Song Liu
2024-11-16 3:50 ` Yu Kuai
2024-11-17 18:32 ` John Garry
2024-11-14 8:22 ` John Garry [this message]
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=8b3c057b-123c-4e57-9221-447ff1b073a6@oracle.com \
--to=john.g.garry@oracle.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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
all inboxes | Powered by JetHome®