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: Fri, 20 May 2005 18:26:24 +0900 (JST)	[thread overview]
Message-ID: <20050520.182624.67793132.taka@valinux.co.jp> (raw)
In-Reply-To: <20050519003008.GC25076@chandralinux.beaverton.ibm.com>

Hi Chandra,

> Here is the latest CKRM Memory controller patch against the patchset Gerrit
> released on 05/05/05.
    (snip)
> 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
> 	- to make vmscan.c cleaner.

I think it's very heavy to move all pages, which are mapped to removing
regions, to new classes every time. It always happens when doing exec()
or exit(), while munmap and closing file don't.
Pages associating with libc.so or text of shells might move around
the all classes.

IMHO, it would be enough to just leave them as they are.
These pages would be released a little later if no class touch them,
or they might be accessed from another class to migrate another
class, or they might reused in the same class.

I feel it's not needed to move these pages in hurry.
I prefer the implementation light.
What do you think?


BTW, the memory controller would be a good new to video streaming
guys, I guess.


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>

  parent reply	other threads:[~2005-05-20  9:26 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
2005-05-23 12:54         ` Hirokazu Takahashi
2005-05-20  9:26 ` Hirokazu Takahashi [this message]
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=20050520.182624.67793132.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