From: Hirokazu Takahashi <taka@valinux.co.jp>
To: raybry@engr.sgi.com
Cc: raybry@sgi.com, marcelo.tosatti@cyclades.com, ak@suse.de,
haveblue@us.ibm.com, hch@infradead.org, linux-mm@kvack.org,
nathans@sgi.com, raybry@austin.rr.com,
lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 2.6.12-rc3 4/8] mm: manual page migration-rc2 -- add-sys_migrate_pages-rc2.patch
Date: Fri, 13 May 2005 08:50:34 +0900 (JST) [thread overview]
Message-ID: <20050513.085034.74732081.taka@valinux.co.jp> (raw)
In-Reply-To: <42838742.3030903@engr.sgi.com>
Hi Ray,
> > I just thought of the page, belonging to some file which is
> > mmap()ed to the target process to be migrated. The page may
> > not be accessed and the associated PTE isn't set yet.
> > if vma->vm_file->f_mapping equals page_mapping(page), the page
> > should be migrated.
> >
> > Pages in the swap-cache have the same problem since the related
> > PTEs may be clean.
> >
> > But these cases may be rare and your approach seems to be good
> > enough in most cases.
> >
> >
>
> Well, what could be done would be the following, I suppose:
>
> If follow_page() returns NULL and the vma maps a file, we could
> lookup the page in the radix tree, and if we find it, and if it
> is on a node that we are migrating from, we could add the page
> to the set of pages to be migrated.
>
> The disadvantage of this is that we could do a LOT of radix
> tree lookups and find relatively few pages. (Our approach of
How about find_get_pages() for whole mmap()'ed ranges?
With it, you may not need to call follow_page().
> releasing free page cache pages first makes such pages just
> "go away". But we don't have "release free page cache pages"
> in the mainline yet. :-( )
>
> Similarly, if we modified follow_page() (e. g. follow_page_ex())
> to return the pte, check to see if it is a swap pte (!pte_none()
> && !pte_file()), if so then use pte_to_swap_entry() to get
> the swap entry, and then use that to look up the page in the
> swapper space radix tree. Then handle it as above (hmmm...
> will your migration code handle a page in the swap cache?)
Sure. The code can also migrate pages in the swap cache.
> Once again, this could lead to lots of lookups. This is
> especially a concern for a large multithreaded app, since the
> address spaces are the same for each process id, hence we look
> up the same info over and over in each page table scan.
>
> --
> Best Regards,
> Ray
Thanks,
Hirokazu Takahashi.
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-05-12 23:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 4:37 [PATCH 2.6.12-rc3 0/8] mm: manual page migration-rc2 -- overview Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 1/8] mm: manual page migration-rc2 -- xfs-extended-attributes-rc2.patch Ray Bryant
2005-05-11 7:15 ` Christoph Hellwig
2005-05-11 12:10 ` [Lhms-devel] " Ray Bryant
2005-05-11 12:59 ` Andi Kleen
2005-05-11 18:43 ` Ray Bryant
2005-05-11 19:32 ` Andi Kleen
2005-05-11 20:00 ` Christoph Hellwig
2005-05-11 22:04 ` Ray Bryant
2005-05-12 10:45 ` Christoph Hellwig
2005-05-17 4:22 ` Ray Bryant
2005-05-18 6:20 ` Paul Jackson
2005-05-18 14:49 ` Ray Bryant
2005-05-20 22:26 ` Ray Bryant
2005-05-23 17:50 ` Steve Longerbeam
2005-05-24 4:53 ` Ray Bryant
2005-05-24 20:59 ` Christoph Lameter
2005-05-24 21:04 ` Martin J. Bligh
2005-05-25 6:42 ` Ray Bryant
2005-05-28 8:40 ` Christoph Hellwig
2005-05-28 16:12 ` Ray Bryant
2005-05-11 19:50 ` Christoph Hellwig
2005-05-11 21:30 ` Ray Bryant
2005-05-12 9:55 ` Christoph Hellwig
2005-05-12 15:47 ` Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 2/8] mm: manual page migration-rc2 -- xfs-migrate-page-rc2.patch Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 3/8] mm: manual page migration-rc2 -- add-node_map-arg-to-try_to_migrate_pages-rc2.patch Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 4/8] mm: manual page migration-rc2 -- add-sys_migrate_pages-rc2.patch Ray Bryant
2005-05-11 8:24 ` Christoph Hellwig
2005-05-18 19:07 ` Ray Bryant
2005-05-28 9:14 ` Christoph Hellwig
2005-05-28 15:53 ` Ray Bryant
2005-05-11 13:23 ` Hirokazu Takahashi
2005-05-11 13:26 ` Hirokazu Takahashi
2005-05-11 14:06 ` Ray Bryant
2005-05-12 6:41 ` Hirokazu Takahashi
2005-05-12 16:41 ` Ray Bryant
2005-05-12 23:50 ` Hirokazu Takahashi [this message]
2005-05-13 9:59 ` [Lhms-devel] " Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 5/8] mm: manual page migration-rc2 -- sys_migrate_pages-xattr-support-rc2.patch Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 6/8] mm: manual page migration-rc2 -- sys_migrate_pages-mempolicy-migration-rc2.patch Ray Bryant
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 7/8] mm: manual page migration-rc2 -- sys_migrate_pages-cpuset-support-rc2.patch Ray Bryant
2005-05-11 12:37 ` Paul Jackson
2005-05-11 14:20 ` Ray Bryant
2005-05-11 18:55 ` [Lhms-devel] " Paul Jackson
2005-05-11 4:38 ` [PATCH 2.6.12-rc3 8/8] mm: manual page migration-rc2 -- sys_migrate_pages-permissions-check-rc2.patch Ray Bryant
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=20050513.085034.74732081.taka@valinux.co.jp \
--to=taka@valinux.co.jp \
--cc=ak@suse.de \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nathans@sgi.com \
--cc=raybry@austin.rr.com \
--cc=raybry@engr.sgi.com \
--cc=raybry@sgi.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