From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: man page update (fcntl(2) new set/get write hints)
Date: Thu, 24 Aug 2017 08:39:27 -0600 [thread overview]
Message-ID: <39f20b08-9a35-652e-4ae9-96f3cb8e5679@kernel.dk> (raw)
In-Reply-To: <feffa54b-d1b4-02e3-5a24-0a8e51f96762-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 08/23/2017 04:41 PM, Michael Kerrisk (man-pages) wrote:
> Hello Jens,
>
> On 07/31/2017 05:24 PM, Jens Axboe wrote:
>> Hi Michael,
>>
>> Not sure what the best way to submit this is, but I wrote an
>> update for the fcntl man page to cover the new set/get write
>> hints commands that are added in 4.13. Attaching the patch, but
>> you can also find it below, in a fork of your github repo:
>>
>> https://github.com/axboe/man-pages/commits/fcntl-write-hints
>
> Thanks for the patch. Some questions below.
>
>> From 3eee36f14a650e50f14b42ae1d4fec33e78e6254 Mon Sep 17 00:00:00 2001
>> From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
>> Date: Mon, 26 Jun 2017 16:58:29 -0600
>> Subject: [PATCH] man2/fcntl.2: add description of new read/write hint commands
>>
>> This adds a description of the new read/write hint commands:
>>
>> F_GET_RW_HINT Get inode read/write hint
>> F_SET_RW_HINT Set inode read/write hint
>> F_GET_FILE_RW_HINT Get file read/write hint
>> F_SET_FILE_RW_HINT Set file read/write hint
>>
>> and the currently available values, as of Linux 4.13.
>>
>> Signed-off-by: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
>> ---
>> man2/fcntl.2 | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 58 insertions(+)
>>
>> diff --git a/man2/fcntl.2 b/man2/fcntl.2
>> index 70758d2fcd99..07eacc9564fa 100644
>> --- a/man2/fcntl.2
>> +++ b/man2/fcntl.2
>> @@ -5,6 +5,7 @@
>> .\" and Copyright (C) 2002-2010, 2014 Michael Kerrisk;
>> .\" and Copyright (C) 2014 Jeff Layton
>> .\" and Copyright (C) 2014 David Herrmann
>> +.\" and Copyright (C) 2017 Jens Axboe
>> .\"
>> .\" %%%LICENSE_START(VERBATIM)
>> .\" Permission is granted to make and distribute verbatim copies of this
>> @@ -61,6 +62,8 @@
>> .\" Document F_SETPIPE_SZ and F_GETPIPE_SZ.
>> .\" 2014-07-08, David Herrmann <dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> .\" Document F_ADD_SEALS and F_GET_SEALS
>> +.\" 2017-06-26, Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
>> +.\" Document F_{GET,SET}_RW_HINT and F_{GET,SET}_FILE_RW_HINT
>> .\"
>> .TH FCNTL 2 2017-05-03 "Linux" "Linux Programmer's Manual"
>> .SH NAME
>> @@ -1490,6 +1493,61 @@ Furthermore, if there are any asynchronous I/O operations
>> .RB ( io_submit (2))
>> pending on the file,
>> all outstanding writes will be discarded.
>> +.SS File read/write hints
>> +Write life time hints can be used to inform the kernel about the relative
>> +expected life time of writes on a given inode or file. An application may
>> +use this interface for separating writes into different write classes,
>> +so that multiple users or applications running on a single storage back-end
>> +can aggregate their IO patterns in a consistent manner. However, there are
>> +no functional semantics implied by these flags, and different IO classes
>> +can use the write life time hints in arbitrary ways so long as they are used
>> +consistently.
>
> I read the above, and it is still not clear to me what a "write lifetime"
> is. Can you add some text to explain? (I'm guessing that it means the
> amount of time before the data is overwritten by another write, but I'm
> not sure of that, and it needs to be more explicit in the text.)
You are right, it's exactly what it refers to. It's essentially data
lifetime hints for a write command. I'd be happy to take suggestions to
improve the description of it.
>> +.TP
>> +.BR F_GET_RW_HINT " (\fIuint64_t\fP; since Linux 4.13)"
>> +Returns the value of the read/write hint associated with the underlying inode
>> +for the file descriptor.
>> +.TP
>> +.BR F_SET_RW_HINT " (\fIuint64_t\fP; since Linux 4.13)"
>> +Sets the read/write hint value associated with the underlying inode for the
>> +file descriptor.
>> +.TP
>> +.BR F_GET_FILE_RW_HINT " (\fIuint64_t\fP; since Linux 4.13)"
>> +Returns the value of the read/write hint associated with the file descriptor.
>
> Do you mean here "file descriptor" or "file description (i.e., the
> open file handle)? Maybe you mean the former, but I want to confirm.
I do mean file descriptor.
>> +.TP
>> +.BR F_SET_FILE_RW_HINT " (\fIuint64_t\fP; since Linux 4.13)"
>> +Sets the read/write hint value associated with the file descriptor.
>
> Same as above comment.
Ditto.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-24 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25b8e025-d49b-e033-5ba3-f6967a6a970f@kernel.dk>
[not found] ` <25b8e025-d49b-e033-5ba3-f6967a6a970f-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-08-23 22:41 ` man page update (fcntl(2) new set/get write hints) Michael Kerrisk (man-pages)
[not found] ` <feffa54b-d1b4-02e3-5a24-0a8e51f96762-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-24 14:39 ` Jens Axboe [this message]
[not found] ` <39f20b08-9a35-652e-4ae9-96f3cb8e5679-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-08-24 22:10 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkizCBiky9QM0-oyP3taGKCDTjAP--SCgqZ3pC8Kz=PnPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-25 20:43 ` Jens Axboe
[not found] ` <580f238c-4c3d-eddc-5330-19f8a971bce1-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-08-25 20:51 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkhJysMFycC8xxjQ8s=+ABryEmWTFUopTWoan04icGibAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-25 20:55 ` Jens Axboe
[not found] ` <6d17003b-87a1-43c8-87bf-80842b4fabf7-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-08-28 19:19 ` Michael Kerrisk (man-pages)
[not found] ` <68b812bd-a861-2ed0-e207-fb0a9bbce923-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-28 20:15 ` Jens Axboe
[not found] ` <6ad54bed-75fa-5153-004e-c4a8a1c87a35-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-08-28 21:16 ` Michael Kerrisk (man-pages)
[not found] ` <778a45d3-8bee-aa8b-86bd-c7e6cd7e5c60-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-03 0:45 ` Michael Kerrisk (man-pages)
[not found] ` <e281652b-44d7-1c59-35ea-63836d6532dd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-11 14:31 ` Michael Kerrisk (man-pages)
2017-08-28 9:07 ` Florian Weimer
[not found] ` <02cf5c20-bb36-29e3-01e2-3a90e8272c70-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-28 16:13 ` Jens Axboe
2017-08-28 21:13 ` 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=39f20b08-9a35-652e-4ae9-96f3cb8e5679@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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