From: Shaohua Li <shaohua.li@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm <linux-mm@kvack.org>,
"riel@redhat.com" <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Wu, Fengguang" <fengguang.wu@intel.com>
Subject: Re: [patch]vmscan: protect exectuable page from inactive list scan
Date: Thu, 30 Sep 2010 08:04:12 +0800 [thread overview]
Message-ID: <1285805052.1773.9.camel@shli-laptop> (raw)
In-Reply-To: <20100929101704.GB2618@cmpxchg.org>
On Wed, 2010-09-29 at 18:17 +0800, Johannes Weiner wrote:
> On Wed, Sep 29, 2010 at 10:57:40AM +0800, Shaohua Li wrote:
> > With commit 645747462435, pte referenced file page isn't activated in inactive
> > list scan. For VM_EXEC page, if it can't get a chance to active list, the
> > executable page protect loses its effect. We protect such page in inactive scan
> > here, now such page will be guaranteed cached in a full scan of active and
> > inactive list, which restores previous behavior.
>
> This change was in the back of my head since the used-once detection
> was merged but there were never any regressions reported that would
> indicate a requirement for it.
The executable page protect is to improve responsibility. I would expect
it's hard for user to report such regression.
> Does this patch fix a problem you observed?
No, I haven't done test where Fengguang does in commit 8cab4754d24a0f.
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -608,8 +608,15 @@ static enum page_references page_check_references(struct page *page,
> > * quickly recovered.
> > */
> > SetPageReferenced(page);
> > -
> > - if (referenced_page)
> > + /*
> > + * Identify pte referenced and file-backed pages and give them
> > + * one trip around the active list. So that executable code get
> > + * better chances to stay in memory under moderate memory
> > + * pressure. JVM can create lots of anon VM_EXEC pages, so we
> > + * ignore them here.
>
> PTE-referenced PageAnon() pages are activated unconditionally a few
> lines further up, so the page_is_file_cache() check filters only shmem
> pages. I doubt this was your intention...?
This is intented. the executable page protect is just to protect
executable file pages. please see 8cab4754d24a0f.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-09-30 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 2:57 Shaohua Li
2010-09-29 10:17 ` Johannes Weiner
2010-09-30 0:04 ` Shaohua Li [this message]
2010-09-30 2:27 ` KOSAKI Motohiro
2010-09-30 2:57 ` Wu Fengguang
2010-09-30 3:04 ` KOSAKI Motohiro
2010-09-30 3:20 ` Shaohua Li
2010-09-30 3:32 ` Wu Fengguang
2010-09-30 4:46 ` KOSAKI Motohiro
2010-09-30 5:46 ` Shaohua Li
2010-09-30 6:00 ` KOSAKI Motohiro
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=1285805052.1773.9.camel@shli-laptop \
--to=shaohua.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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