linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hirokazu Takahashi <taka@valinux.co.jp>
To: sekharan@us.ibm.com
Cc: ckrm-tech@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: [PATCH 0/6] CKRM: Memory controller for CKRM
Date: Mon, 23 May 2005 20:31:59 +0900 (JST)	[thread overview]
Message-ID: <20050523.203159.01016468.taka@valinux.co.jp> (raw)
In-Reply-To: <20050521000700.GA30327@chandralinux.beaverton.ibm.com>

Hi Chandra,

> > > On Thu, May 19, 2005 at 10:43:25AM +0900, Hirokazu Takahashi wrote:
> > > > Hello,
> > > > 
> > > > It just looks like that once kswapd moves pages between the active lists
> > > > and the inactive lists, the pages happen to belong to the class
> > > > to which kswapd belong.
> > > 
> > > In refill_inactive_zone()(where pages are moved from active to inactive
> > > list), ckrm_zone(where the page came from) is where the inactive pages are 
> > > moved to.
> > 
> > Ah, I understood.
> > You have changed these functions not to call add_page_to_active_list() or
> > add_page_to_inactive_list() anymore.
> > 
> > Still, there may remain problems that mark_page_accessed() calls
> > add_page_to_active_list() to move pages between classes.
> > I guess this isn't good manner since some functions which call
> > mark_page_accessed(), like unmap_mapping_range_vma() or get_user_pages(),
> > may refer pages of the other classes.
> 
> You mean these functions are not called in the context of the task that
> is in the stack ?

No, in some cases though it doesn't seem to be serious.

You may take a look at unmap_mapping_range_tree() as an example.
It traverses mapping->i_mmap to find all related vma's to be
unmapped. And get_user_pages() has the parameter that indicates
which process space should be accessed.

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>

  reply	other threads:[~2005-05-23 11:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  0:30 Chandra Seetharaman
2005-05-19  1:43 ` Hirokazu Takahashi
2005-05-19 16:33   ` Chandra Seetharaman
2005-05-20  5:29     ` Hirokazu Takahashi
2005-05-21  0:07       ` Chandra Seetharaman
2005-05-23 11:31         ` Hirokazu Takahashi [this message]
2005-05-23 12:54         ` Hirokazu Takahashi
2005-05-20  9:26 ` Hirokazu Takahashi
2005-05-21  0:11   ` Chandra Seetharaman
2005-05-23 13:20     ` Hirokazu Takahashi
2005-05-27 13:16 ` Virtual NUMA machine and CKRM Hirokazu Takahashi
2005-05-27 14:09   ` Martin J. Bligh
2005-05-28  7:40     ` Hirokazu Takahashi
2005-05-27 14:15   ` [ckrm-tech] " Dave Hansen
2005-05-31 19:13     ` Chandra Seetharaman
2005-05-31 19:10   ` Chandra Seetharaman
2005-06-01  5:28   ` [ckrm-tech] " YAMAMOTO Takashi
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24 22:18 [PATCH 0/6] CKRM: Memory controller for CKRM Chandra Seetharaman
2005-04-02  3:10 Chandra Seetharaman

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=20050523.203159.01016468.taka@valinux.co.jp \
    --to=taka@valinux.co.jp \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=linux-mm@kvack.org \
    --cc=sekharan@us.ibm.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