From: John Garry <john.g.garry@oracle.com>
To: 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,
John Garry <john.g.garry@oracle.com>
Subject: [PATCH v4 0/3] man2: Document RWF_ATOMIC
Date: Wed, 17 Jul 2024 09:36:16 +0000 [thread overview]
Message-ID: <20240717093619.3148729-1-john.g.garry@oracle.com> (raw)
Document RWF_ATOMIC flag for pwritev2().
RWF_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 merged into Linus' tree, to be released in
v6.11
Differences to v3:
- Formatting changes (Alex)
- semantic newlines
- Add missing .TP in statx
- Combine description of atomic write unit min and max
- misc others
Differences to v2:
- rebase
Differences to v1:
- Add statx max segments param
- Expand readv.2 description
- Document EINVAL
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 | 19 +++++++++++
man/man2/readv.2 | 76 ++++++++++++++++++++++++++++++++++++++++++++
man/man2/statx.2 | 27 ++++++++++++++++
3 files changed, 122 insertions(+)
--
2.31.1
next reply other threads:[~2024-07-17 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 9:36 John Garry [this message]
2024-07-17 9:36 ` [PATCH v4 1/3] statx.2: Document STATX_WRITE_ATOMIC John Garry
2024-07-17 21:36 ` Darrick J. Wong
2024-07-17 9:36 ` [PATCH v4 2/3] readv.2: Document RWF_ATOMIC flag John Garry
2024-07-17 21:44 ` Darrick J. Wong
2024-07-18 14:07 ` John Garry
2024-07-18 15:05 ` Darrick J. Wong
2024-07-17 9:36 ` [PATCH v4 3/3] io_submit.2: Document RWF_ATOMIC John Garry
2024-07-17 21:44 ` Darrick J. Wong
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=20240717093619.3148729-1-john.g.garry@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.