From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, mel@csn.ul.ie, y-goto@jp.fujitsu.com,
hugh@veritas.com
Subject: Re: memory unplug v4 intro [1/6] migration without mm->sem
Date: Fri, 8 Jun 2007 14:54:35 +0900 [thread overview]
Message-ID: <20070608145435.4fa7c9b6.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706072242500.28618@schroedinger.engr.sgi.com>
On Thu, 7 Jun 2007 22:47:08 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> > static inline void anon_vma_lock(struct vm_area_struct *vma)
> > {
> > struct anon_vma *anon_vma = vma->anon_vma;
>
> Could you fold as much as possible into mm/migrate.c?
>
Ah, maybe ok. But scattering codes around rmap in several files is ok ?
> > +void anon_vma_release(struct anon_vma *anon_vma, struct vm_area_struct *holder)
> > +{
> > + if (!anon_vma)
> > + return;
> > + BUG_ON(anon_vma != holder->anon_vma);
> > + anon_vma_unlink(holder);
> > +}
> > +#endif
>
> This is mostly also specific to page migration?
>
yes.
> > @@ -333,6 +362,8 @@ static int page_referenced_anon(struct p
> >
> > mapcount = page_mapcount(page);
> > list_for_each_entry(vma, &anon_vma->head, anon_vma_node) {
> > + if (is_dummy_vma(vma))
> > + continue;
> > referenced += page_referenced_one(page, vma, &mapcount);
> > if (!mapcount)
> > break;
> > @@ -864,6 +895,8 @@ static int try_to_unmap_anon(struct page
> > return ret;
> >
> > list_for_each_entry(vma, &anon_vma->head, anon_vma_node) {
> > + if (is_dummy_vma(vma))
> > + continue;
> > ret = try_to_unmap_one(page, vma, migration);
> > if (ret == SWAP_FAIL || !page_mapped(page))
> > break;
>
> Could you avoid these checks by having page_referend_one fail
> appropriately on the dummy vma?
>
Hmm, Is this better ?
==
static int page_referenced_one(struct page *page,
struct vm_area_struct *vma, unsigned int *mapcount)
{
struct mm_struct *mm = vma->vm_mm;
unsigned long address;
pte_t *pte;
spinlock_t *ptl;
int referenced = 0;
+ if(is_dummy_vma(vma))
+ return 0;
==
-Kame
--
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-06-08 5:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 5:35 memory unplug v4 intro [0/6] KAMEZAWA Hiroyuki
2007-06-08 5:38 ` memory unplug v4 intro [1/6] migration without mm->sem KAMEZAWA Hiroyuki
2007-06-08 5:47 ` Christoph Lameter
2007-06-08 5:54 ` KAMEZAWA Hiroyuki [this message]
2007-06-08 5:57 ` Christoph Lameter
2007-06-08 6:06 ` KAMEZAWA Hiroyuki
2007-06-08 6:44 ` Christoph Lameter
2007-06-08 7:01 ` KAMEZAWA Hiroyuki
2007-06-08 7:21 ` Christoph Lameter
2007-06-08 7:25 ` KAMEZAWA Hiroyuki
2007-06-08 5:39 ` memory unplug v4 [2/6] lru isolation race fix KAMEZAWA Hiroyuki
2007-06-08 5:52 ` Christoph Lameter
2007-06-08 5:58 ` KAMEZAWA Hiroyuki
2007-06-08 5:58 ` Christoph Lameter
2007-06-08 5:40 ` memory unplug v4 intro [3/6] walk memory resources KAMEZAWA Hiroyuki
2007-06-08 5:41 ` memory unplug v4 intro [4/6] page isolation KAMEZAWA Hiroyuki
2007-06-08 13:24 ` Mel Gorman
2007-06-08 13:59 ` KAMEZAWA Hiroyuki
2007-06-08 5:43 ` memory unplug v4 intro [5/6] page offlining KAMEZAWA Hiroyuki
2007-06-08 5:43 ` memory unplug v4 intro [6/6] ia64 interface KAMEZAWA Hiroyuki
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=20070608145435.4fa7c9b6.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=y-goto@jp.fujitsu.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