From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.g.garry@oracle.com>
Cc: axboe@kernel.dk, song@kernel.org, yukuai3@huawei.com, hch@lst.de,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, martin.petersen@oracle.com
Subject: Re: [PATCH v5 0/5] RAID 0/1/10 atomic write support
Date: Mon, 18 Nov 2024 20:37:22 -0500 [thread overview]
Message-ID: <yq1jzd0rolu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20241118105018.1870052-1-john.g.garry@oracle.com> (John Garry's message of "Mon, 18 Nov 2024 10:50:13 +0000")
John,
> 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).
LGTM.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-11-19 1:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 10:50 [PATCH v5 0/5] RAID 0/1/10 atomic write support John Garry
2024-11-18 10:50 ` [PATCH v5 1/5] block: Add extra checks in blk_validate_atomic_write_limits() John Garry
2024-11-18 10:50 ` [PATCH v5 2/5] block: Support atomic writes limits for stacked devices John Garry
2024-11-18 10:50 ` [PATCH v5 3/5] md/raid0: Atomic write support John Garry
2024-11-18 10:50 ` [PATCH v5 4/5] md/raid1: " John Garry
2024-11-18 10:50 ` [PATCH v5 5/5] md/raid10: " John Garry
2024-11-19 1:37 ` Martin K. Petersen [this message]
2024-11-19 17:05 ` [PATCH v5 0/5] RAID 0/1/10 atomic " John Garry
2024-11-19 17:29 ` Jens Axboe
2024-11-19 17:45 ` John Garry
2024-11-19 17:30 ` Jens Axboe
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=yq1jzd0rolu.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--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=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).