From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
Mike Christie <mchristi@redhat.com>,
linux-api@vger.kernel.org, david@fromorbit.com, mhocko@suse.com,
masato.suzuki@wdc.com, damien.lemoal@wdc.com,
darrick.wong@oracle.com, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH] prctl.2: doc PR_SET/GET_IO_FLUSHER - V4
Date: Thu, 2 Apr 2020 14:16:10 +0200 [thread overview]
Message-ID: <5f2bf1c2-4e3e-2472-5035-a6842901b8c8@gmail.com> (raw)
In-Reply-To: <9eab1b92-6a44-616a-44b2-f1ee6475f6f0@acm.org>
On 4/2/20 5:46 AM, Bart Van Assche wrote:
> On 2020-04-01 19:08, Mike Christie wrote:
>> +.TP
>> +.B PR_GET_IO_FLUSHER (Since Linux 5.6)
>> +Return as the function result 1 if the caller is in the IO_FLUSHER state and
>> +0 if not.
>
> Although I'm not at all a language expert, the word order at the start
> of the above sentence seems a bit weird to me?
Thanks for spotting that Bart. I changed the text to:
If a user process is involved in the block layer or
filesystem I/O path, and can allocate memory while process‐
ing I/O requests it must set arg2 to 1. This will put the
process in the IO_FLUSHER state, which allows it special
treatment to make progress when allocating memory. If arg2
is 0, the process will clear the IO_FLUSHER state, and the
default behavior will be used.
Cheers,
Michael
--
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:[~2020-04-02 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 2:08 [PATCH] prctl.2: doc PR_SET/GET_IO_FLUSHER - V4 Mike Christie
2020-04-02 3:46 ` Bart Van Assche
2020-04-02 12:16 ` Michael Kerrisk (man-pages) [this message]
2020-04-02 14:01 ` Michael Christie
2020-04-02 20:12 ` Michael Kerrisk (man-pages)
2020-04-02 6:47 ` Michal Hocko
2020-04-02 12:16 ` Michael Kerrisk (man-pages)
2020-04-02 12:16 ` Michael Kerrisk (man-pages)
2020-04-04 21:07 ` Mike Christie
2020-04-06 11:00 ` 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=5f2bf1c2-4e3e-2472-5035-a6842901b8c8@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=masato.suzuki@wdc.com \
--cc=mchristi@redhat.com \
--cc=mhocko@suse.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).