linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.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: Thu, 7 Jun 2007 22:47:08 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706072242500.28618@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070608143844.569c2804.kamezawa.hiroyu@jp.fujitsu.com>

On Fri, 8 Jun 2007, KAMEZAWA Hiroyuki wrote:

> Index: devel-2.6.22-rc4-mm2/include/linux/rmap.h
> ===================================================================
> --- devel-2.6.22-rc4-mm2.orig/include/linux/rmap.h
> +++ devel-2.6.22-rc4-mm2/include/linux/rmap.h
> @@ -42,6 +42,36 @@ static inline void anon_vma_free(struct 
>  	kmem_cache_free(anon_vma_cachep, anon_vma);
>  }
>  
> +#ifdef  CONFIG_MIGRATION
> +/*
> + * anon_vma->head works as refcnt for anon_vma struct.
> + * Migration needs one reference to anon_vma while unmapping -> remapping.
> + * dummy vm_area_struct is used for adding one ref to anon_vma.
> + *
> + * This means a list-walker of anon_vma->head have to check vma is dummy
> + * or not. please use is_dummy_vma() for check.
> + */
> +
> +extern struct anon_vma *anon_vma_hold(struct page *, struct vm_area_struct *);
> +extern void anon_vma_release(struct anon_vma *, struct vm_area_struct *);
> +
> +static inline void init_dummy_vma(struct vm_area_struct *vma)
> +{
> +	vma->vm_mm = NULL;
> +}
> +
> +static inline int is_dummy_vma(struct vm_area_struct *vma)
> +{
> +	if (unlikely(vma->vm_mm == NULL))
> +		return 1;
> +	return 0;
> +}
> +#else
> +static inline int is_dummy_vma(struct vm_area_struct *vma) {
> +	return 0;
> +}
> +#endif
> +
>  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?

> Index: devel-2.6.22-rc4-mm2/mm/rmap.c
> ===================================================================
> --- devel-2.6.22-rc4-mm2.orig/mm/rmap.c
> +++ devel-2.6.22-rc4-mm2/mm/rmap.c
> @@ -203,6 +203,35 @@ static void page_unlock_anon_vma(struct 
>  	spin_unlock(&anon_vma->lock);
>  	rcu_read_unlock();
>  }
> +#ifdef CONFIG_MIGRATION
> +/*
> + * Record anon_vma in holder->anon_vma.
> + * Returns 1 if vma is linked to anon_vma. otherwise 0.
> + */
> +struct anon_vma *
> +anon_vma_hold(struct page *page, struct vm_area_struct *holder)
> +{
> +	struct anon_vma *anon_vma = NULL;
> +	holder->anon_vma = NULL;
> +	anon_vma = page_lock_anon_vma(page);
> +	if (anon_vma && !list_empty(&anon_vma->head)) {
> +		init_dummy_vma(holder);
> +		holder->anon_vma = anon_vma;
> +		__anon_vma_link(holder);
> +	}
> +	if (anon_vma)
> +		page_unlock_anon_vma(anon_vma);
> +	return holder->anon_vma;
> +}
> +
> +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?

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

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

  reply	other threads:[~2007-06-08  5:47 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 [this message]
2007-06-08  5:54     ` KAMEZAWA Hiroyuki
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=Pine.LNX.4.64.0706072242500.28618@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.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