From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: ckrm-tech@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: [PATCH 0/6] CKRM: Memory controller for CKRM
Date: Thu, 19 May 2005 09:33:38 -0700 [thread overview]
Message-ID: <20050519163338.GC27270@chandralinux.beaverton.ibm.com> (raw)
In-Reply-To: <20050519.104325.13596447.taka@valinux.co.jp>
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.
I don't see how you concluded this. Can you point to the code.
>
> Is this right behavior that you intend?
certainly not :)
>
> > Hello ckrm-tech members,
> >
> > Here is the latest CKRM Memory controller patch against the patchset Gerrit
> > released on 05/05/05.
> >
> > I applied the feedback I got on/off the list. Made few fixes and some
> > cleanups. Details about the changes are in the appripriate patches.
> >
> > It is tested on i386.
> >
> > Currently disabled on NUMA.
> >
> > Hello linux-mm members,
> >
> > These are set of patches that provides the control of memory under the CKRM
> > framework(Details at http://ckrm.sf.net). I eagerly wait for your
> > feedback/comments/suggestions/concerns etc.,
> >
> > To All,
> >
> > I am looking for improvement suggestions
> > - to not have a field in the page data structure for the mem
> > controller
>
> What do you think if you make each class owns inodes instead of pages
> in the page-cache?
>
> > - to make vmscan.c cleaner.
>
>
> Thanks,
> Hirokazu Takahashi.
>
>
>
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
--
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-19 16:40 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 [this message]
2005-05-20 5:29 ` Hirokazu Takahashi
2005-05-21 0:07 ` Chandra Seetharaman
2005-05-23 11:31 ` Hirokazu Takahashi
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=20050519163338.GC27270@chandralinux.beaverton.ibm.com \
--to=sekharan@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
/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