linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>,
	"riel@redhat.com" <riel@redhat.com>,
	Andi Kleen <andi@firstfloor.org>,
	"hughd@google.com" <hughd@google.com>
Subject: Re: [RFC]vmscan: doing page_referenced() in batch way
Date: Wed, 13 Oct 2010 12:53:19 +0800	[thread overview]
Message-ID: <20101013045319.GA11115@sli10-conroe.sh.intel.com> (raw)
In-Reply-To: <20101006131052.e3ae026f.akpm@linux-foundation.org>

On Thu, Oct 07, 2010 at 04:10:52AM +0800, Andrew Morton wrote:
> On Wed, 29 Sep 2010 10:57:33 +0800
> Shaohua Li <shaohua.li@intel.com> wrote:
> 
> > when memory pressure is high, page_referenced() causes a lot of lock contention
> > for anon_vma->lock or mapping->i_mmap_lock. Considering pages from one file
> > usually live side by side in LRU list, we can lock several pages in
> > shrink_page_list() and do batch page_referenced() to avoid some lock/unlock,
> > which should reduce lock contention a lot. The locking rule documented in
> > rmap.c is:
> > page_lock
> > 	mapping->i_mmap_lock
> > 		anon_vma->lock
> > For a batch of pages, we do page lock for all of them first and check their
> > reference, and then release their i_mmap_lock or anon_vma lock. This seems not
> > break the rule to me.
> > Before I further polish the patch, I'd like to know if there is anything
> > preventing us to do such batch here.
Thanks for your time.

> The patch adds quite a bit of complexity, so we'd need to see benchmark
> testing results which justify it, please.
My test only shows around 10% improvements, which is below my expections.
try_to_unmap() causes quite a lot of lock contention for such locks, and makes
the page_referenced() batch not quite helpful. Looks we can do batch try_to_unmap()
too. I'll report back later when I have data with try_to_unmap() batched.

Thanks,
Shaohua

--
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>

      parent reply	other threads:[~2010-10-13  4:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29  2:57 [RFC]vmscan: doing page_referenced() in batch way Shaohua Li
2010-10-06 20:10 ` Andrew Morton
2010-10-10 17:10   ` Rik van Riel
2010-10-11  0:49     ` Shaohua Li
2010-10-13  4:53   ` Shaohua Li [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=20101013045319.GA11115@sli10-conroe.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=hughd@google.com \
    --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;
as well as URLs for NNTP newsgroup(s).