From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Cc: Eelco Chaudron <echaudro@redhat.com>,
Aaron Conole <aconole@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
dpdk stable <stable@dpdk.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [dpdk-stable] [PATCH] mem: mark pages as not accessed when reserving VA
Date: Fri, 13 Mar 2020 10:59:29 +0100 [thread overview]
Message-ID: <CAJFAV8y6_SkhZnVCHVu_QGC=zPrEQekOY_GX1SZ_kpNhL28mXA@mail.gmail.com> (raw)
In-Reply-To: <20200309145442.28926-1-david.marchand@redhat.com>
On Mon, Mar 9, 2020 at 3:55 PM David Marchand <david.marchand@redhat.com> wrote:
>
> When the memory allocator reserves virtual addresses, it still does not
> know what they will be used for.
> Besides, huge areas are reserved for memory hotplug in multiprocess
> setups. But most of the pages are unused in the whole life of the
> processes.
>
> Change protection mode to PROT_NONE when only reserving VA.
> The memory allocator already switches to the right mode when making use
> of it.
>
> It also has the nice effect of getting those pages skipped by the kernel
> when calling mlockall() or when a coredump gets generated.
>
> Cc: stable@dpdk.org
>
> Suggested-by: Andrea Arcangeli <aarcange@redhat.com>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Aaron Conole <aconole@redhat.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied.
--
David Marchand
prev parent reply other threads:[~2020-03-13 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 14:54 David Marchand
2020-03-09 15:27 ` Maxime Coquelin
2020-03-10 13:57 ` Aaron Conole
2020-03-10 16:26 ` Burakov, Anatoly
2020-03-13 9:59 ` David Marchand [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='CAJFAV8y6_SkhZnVCHVu_QGC=zPrEQekOY_GX1SZ_kpNhL28mXA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aarcange@redhat.com \
--cc=aconole@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=echaudro@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.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).