From: Nick Piggin <npiggin@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 3/4] mm: move mlocked pages off the LRU
Date: Tue, 20 Mar 2007 04:32:14 +0100 [thread overview]
Message-ID: <20070320033214.GA30766@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0703191325120.8150@schroedinger.engr.sgi.com>
On Mon, Mar 19, 2007 at 01:35:56PM -0700, Christoph Lameter wrote:
> On Mon, 12 Mar 2007, Nick Piggin wrote:
>
> > @@ -859,9 +873,23 @@ static int try_to_unmap_anon(struct page
> > ret = try_to_unmap_one(page, vma, migration);
> > if (ret == SWAP_FAIL || !page_mapped(page))
> > break;
> > + if (ret == SWAP_MLOCK) {
> > + if (down_read_trylock(&vma->vm_mm->mmap_sem)) {
> > + if (vma->vm_flags & VM_LOCKED) {
> > + mlock_vma_page(page);
> > + mlocked++;
> > + }
>
> Ok. we move mlocked pages off the LRU here...
>
> > + up_read(&vma->vm_mm->mmap_sem);
> > + }
>
> ^^^ else ret = SWAP_AGAIN ?
> > + }
> > }
> > -
> > page_unlock_anon_vma(anon_vma);
> > +
> > + if (mlocked)
> > + ret = SWAP_MLOCK;
> > + else if (ret == SWAP_MLOCK)
> > + ret = SWAP_AGAIN;
>
> So if we failed to mlock (because we could not acquire mmap_sem) then we
> fall back to SWAP_AGAIN. Would it not be cleaner to change ret to
> SWAP_AGAIN as I noted above?
They aren't equivalent though. It may be cleaner to instead do the mlock
in try_to_unmap_one. Perhaps.
> > Index: linux-2.6/mm/mempolicy.c
> > ===================================================================
> > --- linux-2.6.orig/mm/mempolicy.c
> > +++ linux-2.6/mm/mempolicy.c
> > + struct pagevec migrate;
> > + int i;
> > +
> > +resume:
> > + pagevec_init(&migrate, 0);
>
> Thats new. use a pagevec.
>
> > @@ -254,12 +261,26 @@ static int check_pte_range(struct vm_are
> >
> > if (flags & MPOL_MF_STATS)
> > gather_stats(page, private, pte_dirty(*pte));
> > - else if (flags & (MPOL_MF_MOVE | MPOL_MF_MOVE_ALL))
> > - migrate_page_add(page, private, flags);
> > - else
> > + else if (flags & (MPOL_MF_MOVE | MPOL_MF_MOVE_ALL)) {
> > + if (!pagevec_add(&migrate, page)) {
>
> pagevec adds increases refcount right?
No.
> How can isolate_page_lru cope
> with the refcount increase? Wont work.
>
>
> > + pte_unmap_unlock(orig_pte, ptl);
> > + for (i = 0; i < pagevec_count(&migrate); i++) {
> > + struct page *page = migrate.pages[i];
> > + if (PageMLock(page)) {
> > + lock_page(page);
> > + clear_page_mlock(page);
> > + unlock_page(page);
> > + lru_add_drain();
> > + }
>
> If you do not take the refcount in pagevec_add then there is nothing here
> holding the page except for the pte reference.
Good point.
>
> > + migrate_page_add(page, private, flags);
>
> migrate_page_add is going to fail always. Migrate_page_add should make the
> decision if a page can be taken off the LRU or not. That is why we could
> not use a pagevec.
I don't really follow you.
>
> > @@ -363,6 +384,7 @@ check_range(struct mm_struct *mm, unsign
> > endvma = end;
> > if (vma->vm_start > start)
> > start = vma->vm_start;
> > +
> > err = check_pgd_range(vma, start, endvma, nodes,
> > flags, private);
> > if (err) {
>
> Huh? No changes to migrate.c?
There should have been. Above the mempolicy.c changes.
--
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:[~2007-03-20 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 6:38 [patch 0/4] mlock pages off LRU Nick Piggin
2007-03-12 6:38 ` [patch 1/4] mm: move and rework isolate_lru_page Nick Piggin
2007-03-19 20:10 ` Christoph Lameter
2007-03-12 6:38 ` [patch 2/4] mm: move and rename install_arg_page Nick Piggin
2007-03-12 6:39 ` [patch 3/4] mm: move mlocked pages off the LRU Nick Piggin
2007-03-19 20:35 ` Christoph Lameter
2007-03-20 3:32 ` Nick Piggin [this message]
2007-03-12 6:39 ` [patch 4/4] mm: account mlocked pages Nick Piggin
2007-03-19 20:25 ` Christoph Lameter
2007-03-19 20:39 ` [patch 0/4] mlock pages off LRU Christoph Lameter
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=20070320033214.GA30766@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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