From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Jürg Billeter" <j@bitron.ch>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] readv.2, io_submit.2: Document RWF_APPEND added in Linux 4.16
Date: Thu, 5 Apr 2018 19:49:14 +0200 [thread overview]
Message-ID: <1f559be3-93df-ccdd-02dc-39c83c83a8c9@gmail.com> (raw)
In-Reply-To: <20180328194911.49632-1-j@bitron.ch>
Hello Jürg
Thanks for the patch, but there are some details that are
unexplained in the text and in the kernel commit message.
Does the use of these flags change the file offset? The text
should make this point explicit.
Presumably, when using this flag for pwritev2(), the
'offset' argument of the call is ignored. Presumably, the
same is true for the 'aio_offset' field of the 'iocb'
structure when using io_submit(). This point should be
also be made explicit in the patch.
Would you be willing to revise the patch to include the
answers to these questions?
Cheers,
Michael
On 03/28/2018 09:49 PM, Jürg Billeter wrote:
> Signed-off-by: Jürg Billeter <j@bitron.ch>
> ---
> man2/io_submit.2 | 10 ++++++++++
> man2/readv.2 | 10 ++++++++++
> 2 files changed, 20 insertions(+)
>
> diff --git a/man2/io_submit.2 b/man2/io_submit.2
> index 397fd0b75..79fcdfee4 100644
> --- a/man2/io_submit.2
> +++ b/man2/io_submit.2
> @@ -111,6 +111,16 @@ field of the
> .I io_event
> structure (see
> .BR io_getevents (2)).
> +.TP
> +.BR RWF_APPEND " (since Linux 4.16)"
> +.\" commit e1fc742e14e01d84d9693c4aca4ab23da65811fb
> +Append data to the end of the file.
> +See the description of the flag of the same name in
> +.BR pwritev2 (2)
> +as well as the description of
> +.B O_APPEND
> +in
> +.BR open (2).
> .RE
> .TP
> .I aio_lio_opcode
> diff --git a/man2/readv.2 b/man2/readv.2
> index b3b7b9658..668fba576 100644
> --- a/man2/readv.2
> +++ b/man2/readv.2
> @@ -248,6 +248,16 @@ to
> .BR EAGAIN .
> Currently, this flag is meaningful only for
> .BR preadv2 ().
> +.TP
> +.BR RWF_APPEND " (since Linux 4.16)"
> +.\" commit e1fc742e14e01d84d9693c4aca4ab23da65811fb
> +Provide a per-write equivalent of the
> +.B O_APPEND
> +.BR open (2)
> +flag.
> +This flag is meaningful only for
> +.BR pwritev2 (),
> +and its effect applies only to the data range written by the system call.
> .SH RETURN VALUE
> On success,
> .BR readv (),
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2018-04-05 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 19:49 [PATCH] readv.2, io_submit.2: Document RWF_APPEND added in Linux 4.16 Jürg Billeter
2018-04-05 17:49 ` Michael Kerrisk (man-pages) [this message]
2018-04-06 13:51 ` [PATCH v2] " Jürg Billeter
2018-04-12 9:11 ` Michael Kerrisk (man-pages)
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=1f559be3-93df-ccdd-02dc-39c83c83a8c9@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=j@bitron.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
/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