From: Daniel Colascione <dancol@google.com>
To: dave.hansen@intel.com
Cc: linux-mm@kvack.org, Tim Murray <timmurray@google.com>,
Minchan Kim <minchan@kernel.org>
Subject: Re: Why do we let munmap fail?
Date: Mon, 21 May 2018 15:20:29 -0700 [thread overview]
Message-ID: <CAKOZuetDX905PeLt5cs7e_maSeKHrP0DgM1Kr3vvOb-+n=a7Gw@mail.gmail.com> (raw)
In-Reply-To: <aacd607f-4a0d-2b0a-d8d9-b57c686d24fc@intel.com>
On Mon, May 21, 2018 at 3:12 PM Dave Hansen <dave.hansen@intel.com> wrote:
> On 05/21/2018 03:07 PM, Daniel Colascione wrote:
> > Now let's return to max_map_count itself: what is it supposed to
achieve?
> > If we want to limit application kernel memory resource consumption,
let's
> > limit application kernel memory resource consumption, accounting for it
on
> > a byte basis the same way we account for other kernel objects allocated
on
> > behalf of userspace. Why should we have a separate cap just for the VMA
> > count?
> VMAs consume kernel memory and we can't reclaim them. That's what it
> boils down to.
How is it different from memfd in that respect?
next prev parent reply other threads:[~2018-05-21 22:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 22:07 Why do we let munmap fail? Daniel Colascione
2018-05-21 22:12 ` Dave Hansen
2018-05-21 22:20 ` Daniel Colascione [this message]
2018-05-21 22:29 ` Dave Hansen
2018-05-21 22:35 ` Daniel Colascione
2018-05-21 22:48 ` Dave Hansen
2018-05-21 22:54 ` Daniel Colascione
2018-05-21 23:02 ` Dave Hansen
2018-05-21 23:16 ` Daniel Colascione
2018-05-21 23:32 ` Dave Hansen
2018-05-22 0:00 ` Daniel Colascione
2018-05-22 0:22 ` Matthew Wilcox
2018-05-22 0:38 ` Daniel Colascione
2018-05-22 1:19 ` Theodore Y. Ts'o
2018-05-22 1:41 ` Daniel Colascione
2018-05-22 2:09 ` Daniel Colascione
2018-05-22 2:11 ` Matthew Wilcox
2018-05-22 1:22 ` Matthew Wilcox
2018-05-22 5:34 ` Nicholas Piggin
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='CAKOZuetDX905PeLt5cs7e_maSeKHrP0DgM1Kr3vvOb-+n=a7Gw@mail.gmail.com' \
--to=dancol@google.com \
--cc=dave.hansen@intel.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=timmurray@google.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).