From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Oscar Salvador <osalvador@suse.de>, Jann Horn <jannh@google.com>,
Mike Rapoport <rppt@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v1] madvise.2: Document MADV_POPULATE_READ and MADV_POPULATE_WRITE
Date: Mon, 12 Jul 2021 12:17:52 +0200 [thread overview]
Message-ID: <CAM9Jb+gmCTdbVYX3+Y9F_KRNnYkGNGQvGRJRCBkJX6wjyzmpQQ@mail.gmail.com> (raw)
In-Reply-To: <406695f0-13c8-a052-92d4-44e884eb44af@redhat.com>
> >> +.BR MADV_POPULATE_WRITE " (since Linux 5.14)
> >> +Populate (prefault) page tables writable for the whole range without actually
> >> +writing. Depending on the underlying mapping, preallocate memory or read the
> >
> > Is this read or write?
> > just reading and trying to understand :)
>
> It's reading. Assume you have a file with existing content mapped into a
> process. Once you touch a page (read/write/execute) that maps to blocks
> with existing content, you'll have to load these blocks from disk first.
Got it. Thanks for explaining!
Best regards,
Pankaj
next prev parent reply other threads:[~2021-07-12 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 8:39 [PATCH v1] madvise.2: Document MADV_POPULATE_READ and MADV_POPULATE_WRITE David Hildenbrand
2021-07-12 9:58 ` Pankaj Gupta
2021-07-12 10:03 ` David Hildenbrand
2021-07-12 10:17 ` Pankaj Gupta [this message]
2021-07-25 20:15 ` Alejandro Colomar (man-pages)
2021-07-26 7:11 ` David Hildenbrand
2021-07-12 11:05 ` Pankaj Gupta
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=CAM9Jb+gmCTdbVYX3+Y9F_KRNnYkGNGQvGRJRCBkJX6wjyzmpQQ@mail.gmail.com \
--to=pankaj.gupta.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alx.manpages@gmail.com \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mtk.manpages@gmail.com \
--cc=osalvador@suse.de \
--cc=rppt@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;
as well as URLs for NNTP newsgroup(s).