[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240124112731.28579-4-john.g.garry@oracle.com>
Date: Wed, 24 Jan 2024 11:27:31 +0000
From: John Garry <john.g.garry@...cle.com>
To: linux-kernel@...r.kernel.org, linux-api@...r.kernel.org
Cc: martin.petersen@...cle.com, djwong@...nel.org, david@...morbit.com,
himanshu.madhani@...cle.com, hch@....de, viro@...iv.linux.org.uk,
brauner@...nel.org, jack@...e.cz, John Garry <john.g.garry@...cle.com>
Subject: [PATCH v2 3/3] io_submit.2: Document RWF_ATOMIC
Document RWF_ATOMIC for asynchronous I/O.
Signed-off-by: John Garry <john.g.garry@...cle.com>
---
man2/io_submit.2 | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/man2/io_submit.2 b/man2/io_submit.2
index c53ae9aaf..fb6c4d9bc 100644
--- a/man2/io_submit.2
+++ b/man2/io_submit.2
@@ -140,6 +140,23 @@ as well the description of
.B O_SYNC
in
.BR open (2).
+.TP
+.BR RWF_ATOMIC " (since Linux 6.9)"
+Write a block of data such that a write will never be
+torn from power fail or similar. See the description
+of the flag of the same name in
+.BR pwritev2 (2).
+For usage with
+.BR IOCB_CMD_PWRITEV,
+the upper vector limit is in
+.I stx_atomic_write_segments_max.
+See
+.B STATX_WRITE_ATOMIC
+and
+.I stx_atomic_write_segments_max
+description
+in
+.BR statx (2).
.RE
.TP
.I aio_lio_opcode
--
2.31.1
Powered by blists - more mailing lists