From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Mike Christie <mchristi@redhat.com>
Cc: Linux API <linux-api@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Michal Hocko <mhocko@suse.com>,
masato.suzuki@wdc.com, damien.lemoal@wdc.com,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Bart Van Assche <bvanassche@acm.org>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] prctl.2: doc PR_SET/GET_IO_FLUSHER - V4
Date: Mon, 6 Apr 2020 13:00:00 +0200 [thread overview]
Message-ID: <CAKgNAkigtfzQRNC+DkvmsQaytykhcwGjHucPhsxKhmd+OUkn9Q@mail.gmail.com> (raw)
In-Reply-To: <5E88F713.3050204@redhat.com>
Hi Mike,
On Sat, 4 Apr 2020 at 23:07, Mike Christie <mchristi@redhat.com> wrote:
>
> On 04/02/2020 07:16 AM, Michael Kerrisk (man-pages) wrote:
> > Hello Mike,
> >
> > On 4/2/20 4:08 AM, Mike Christie wrote:
> >> This patch documents the PR_SET_IO_FLUSHER and PR_GET_IO_FLUSHER
> >> prctl commands added to the linux kernel for 5.6 in commit:
> >>
> >> commit 8d19f1c8e1937baf74e1962aae9f90fa3aeab463
> >> Author: Mike Christie <mchristi@redhat.com>
> >> Date: Mon Nov 11 18:19:00 2019 -0600>
> >> prctl: PR_{G,S}ET_IO_FLUSHER to support controlling memory reclaim
> >>
> >> Signed-off-by: Mike Christie <mchristi@redhat.com>
> >
> > I've applied this patch, but I have some questions:
>
> Hey,
>
> Thanks for fixing up the patch for me.
you're welcome.
> > (a) What happens to the IO_FLUSHER setting in the child of fork(2)?
>
> The child will inherit the setting.
>
> > (b) What happens to the IO_FLUSHER setting during an execve(2)?
> > (Is it preserved, reset, something else?)
>
> It's preserved.
Thanks. I added this text:
The IO_FLUSHER state is inherited by a child process cre‐
ated via fork(2) and is preserved across execve(2).
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-04-06 11:01 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)
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) [this message]
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=CAKgNAkigtfzQRNC+DkvmsQaytykhcwGjHucPhsxKhmd+OUkn9Q@mail.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).