From: Eric B Munson <emunson@akamai.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Document interaction between compaction and the unevictable LRU
Date: Tue, 31 Mar 2015 09:23:05 -0400 [thread overview]
Message-ID: <20150331132305.GC17678@akamai.com> (raw)
In-Reply-To: <20150330150939.2e0bd53a3a16ada4cce8ec05@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]
On Mon, 30 Mar 2015, Andrew Morton wrote:
> On Mon, 30 Mar 2015 14:31:14 -0400 Eric B Munson <emunson@akamai.com> wrote:
>
> > The memory compaction code uses the migration code to do most of the
> > work in compaction. However, the compaction code interacts with the
> > unevictable LRU differently than migration code and this difference
> > should be noted in the documentation.
> >
> > --- a/Documentation/vm/unevictable-lru.txt
> > +++ b/Documentation/vm/unevictable-lru.txt
> > @@ -450,6 +451,16 @@ list because of a race between munlock and migration, page migration uses the
> > putback_lru_page() function to add migrated pages back to the LRU.
> >
> >
> > +COMPACTING MLOCKED PAGES
> > +------------------------
> > +
> > +The unevictable LRU can be scanned for compactable regions and the default
> > +behavior is to do so. There is a sysctl to control this behavior (see
> > +Documentation/sysctl/vm.txt). Once scanning of the unevictable LRU is
> > +enabled, the work of compaction is mostly handled by the page migration code
> > +and the same work flow as described in MIGRATING MLOCKED PAGES will apply.
> > +
>
> Thanks. Let's tell people what this sysctl is called?
>
>
> s@There is a sysctl to control@/proc/sys/vm/compact_unevictable_allowed controls@:
>
> --- a/Documentation/vm/unevictable-lru.txt~document-interaction-between-compaction-and-the-unevictable-lru-fix
> +++ a/Documentation/vm/unevictable-lru.txt
> @@ -455,10 +455,11 @@ COMPACTING MLOCKED PAGES
> ------------------------
>
> The unevictable LRU can be scanned for compactable regions and the default
> -behavior is to do so. There is a sysctl to control this behavior (see
> -Documentation/sysctl/vm.txt). Once scanning of the unevictable LRU is
> -enabled, the work of compaction is mostly handled by the page migration code
> -and the same work flow as described in MIGRATING MLOCKED PAGES will apply.
> +behavior is to do so. /proc/sys/vm/compact_unevictable_allowed controls
> +this behavior (see Documentation/sysctl/vm.txt). Once scanning of the
> +unevictable LRU is enabled, the work of compaction is mostly handled by
> +the page migration code and the same work flow as described in MIGRATING
> +MLOCKED PAGES will apply.
>
>
> mmap(MAP_LOCKED) SYSTEM CALL HANDLING
> _
>
That looks good, thanks.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-31 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 18:31 Eric B Munson
2015-03-30 22:09 ` Andrew Morton
2015-03-31 13:23 ` Eric B Munson [this message]
2015-04-04 9:45 ` Jonathan Corbet
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=20150331132305.GC17678@akamai.com \
--to=emunson@akamai.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®