From: John Garry <john.g.garry@oracle.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
axboe@kernel.dk, hch@lst.de, djwong@kernel.org,
dchinner@redhat.com, martin.petersen@oracle.com
Subject: Re: [PATCH v3 0/3] man2: Document RWF_ATOMIC
Date: Wed, 10 Jul 2024 11:07:00 +0100 [thread overview]
Message-ID: <807a74df-5d89-4260-821e-b3968d7d86d4@oracle.com> (raw)
In-Reply-To: <omql3s5mauqxjod5zknewdxjfdsihzv3fi2ypbrzrtkgtcm4yx@peqqpks36isb>
On 09/07/2024 17:43, Alejandro Colomar wrote:
> Hi John,
>
> On Mon, Jul 08, 2024 at 11:42:24AM GMT, John Garry wrote:
>> Document RWF_ATOMIC flag for pwritev2().
>>
>> RWF_ATOMIC atomic is used for enabling torn-write protection.
>>
>> We use RWF_ATOMIC as this is legacy name for similar feature proposed in
>> the past.
>>
>> Kernel support has now been queued in
>> https://lore.kernel.org/linux-block/20240620125359.2684798-1-john.g.garry@oracle.com/
>>
>> Differences to v2:
>> - rebase
>>
>> Differences to v1:
>> - Add statx max segments param
>> - Expand readv.2 description
>> - Document EINVAL
>
> I don't remember having seen v1 or v2. This is the first iteration sent
> to linux-man@, right? (No problem with that; just to confirm.)
Yes, first for linux-man@. An oversight on my part (not to include for
previous iterations), sorry. Please see v1 and v2 at:
https://lore.kernel.org/linux-api/20230929093717.2972367-1-john.g.garry@oracle.com/
https://lore.kernel.org/linux-api/20240124112731.28579-1-john.g.garry@oracle.com/
Thanks,
John
>
>>
>> Himanshu Madhani (2):
>> statx.2: Document STATX_WRITE_ATOMIC
>> readv.2: Document RWF_ATOMIC flag
>>
>> John Garry (1):
>> io_submit.2: Document RWF_ATOMIC
>>
>> man/man2/io_submit.2 | 17 +++++++++++
>> man/man2/readv.2 | 73 +++++++++++++++++++++++++++++++++++++++++++-
>> man/man2/statx.2 | 29 ++++++++++++++++++
>> 3 files changed, 118 insertions(+), 1 deletion(-)
>>
>> --
>> 2.31.1
>>
>
prev parent reply other threads:[~2024-07-10 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 11:42 [PATCH v3 0/3] man2: Document RWF_ATOMIC John Garry
2024-07-08 11:42 ` [PATCH v3 1/3] statx.2: Document STATX_WRITE_ATOMIC John Garry
2024-07-09 16:48 ` Alejandro Colomar
2024-07-10 10:11 ` John Garry
2024-07-10 10:23 ` Alejandro Colomar
2024-07-08 11:42 ` [PATCH v3 2/3] readv.2: Document RWF_ATOMIC flag John Garry
2024-07-09 16:51 ` Alejandro Colomar
2024-07-08 11:42 ` [PATCH v3 3/3] io_submit.2: Document RWF_ATOMIC John Garry
2024-07-09 16:52 ` Alejandro Colomar
2024-07-09 16:53 ` Alejandro Colomar
2024-07-10 10:13 ` John Garry
2024-07-09 16:43 ` [PATCH v3 0/3] man2: " Alejandro Colomar
2024-07-10 10:07 ` 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=807a74df-5d89-4260-821e-b3968d7d86d4@oracle.com \
--to=john.g.garry@oracle.com \
--cc=alx@kernel.org \
--cc=axboe@kernel.dk \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=martin.petersen@oracle.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).