From: Dave Hansen <dave.hansen@intel.com>
To: Armin Rigo <arigo@tunes.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Kenny Simpson <theonetruekenny@gmail.com>,
Michal Hocko <mhocko@suse.cz>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: remap_file_pages() use
Date: Mon, 19 May 2014 10:50:22 -0700 [thread overview]
Message-ID: <537A445E.5030604@intel.com> (raw)
In-Reply-To: <CAMSv6X2EmhgVou03oLTAhpGbNv712mbNWCpL2PXWCXpW9M2nCQ@mail.gmail.com>
On 05/19/2014 09:42 AM, Armin Rigo wrote:
> If there is an official way to know in advance how many remappings our
> process is allowed to perform, then we could adapt as the size
> increases. Or maybe catching ENOMEM and doubling the remapping size
> (in some process-wide synchronization point). All in all, thanks for
> the note: it looks like there are solutions (even if less elegant than
> remap_file_pages from the user's perspective).
We keep the current count as mm->map_count in the kernel, and the limit
is available because it's a sysctl. It wouldn't be hard to dump
mm->map_count out in a /proc file somewhere if it would be useful to
you. Would that work, or is there some other interface that would be
more convenient?
next prev parent reply other threads:[~2014-05-19 17:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 4:03 remap_file_pages() use Kenny Simpson
2014-05-19 13:01 ` Michal Hocko
2014-05-19 14:35 ` Kirill A. Shutemov
2014-05-19 14:38 ` Christoph Hellwig
2014-05-19 15:02 ` Kirill A. Shutemov
2014-05-19 15:11 ` Christoph Hellwig
2014-05-19 15:17 ` Kirill A. Shutemov
2014-05-19 15:42 ` Armin Rigo
2014-05-19 15:53 ` Kirill A. Shutemov
2014-05-19 16:42 ` Armin Rigo
2014-05-19 17:50 ` Dave Hansen [this message]
2014-05-19 22:05 ` Armin Rigo
2014-05-19 16:56 ` Christoph Hellwig
2014-05-19 19:14 ` Richard Weinberger
2014-05-26 0:19 ` Jeff Smith
2014-05-26 9:42 ` Kirill A. Shutemov
2014-05-26 13:24 ` Jeff Smith
2014-05-26 13:35 ` Paolo Bonzini
2014-05-26 13:38 ` Jeff Smith
2014-05-26 13:47 ` Kirill A. Shutemov
2014-05-26 13:52 ` Jeff Smith
2014-05-26 14:16 ` Kirill A. Shutemov
2014-05-26 13:37 ` Kirill A. Shutemov
2014-05-19 17:34 ` Kenny Simpson
2014-05-19 21:24 ` Kirill A. Shutemov
2014-05-21 1:53 ` Kenny Simpson
2014-05-21 3:56 ` Kenny Simpson
2014-05-21 4:32 ` Hugh Dickins
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=537A445E.5030604@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arigo@tunes.org \
--cc=davej@redhat.com \
--cc=hch@infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=peterz@infradead.org \
--cc=theonetruekenny@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.