linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Jacky(GuangXiang Lee)" <gxli@arca.com.cn>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: Christoph Lameter <clameter@sgi.com>,
	climeter@sgi.com, linux-mm@kvack.org
Subject: Re: about page migration on UMA
Date: Wed, 14 Nov 2007 12:31:07 +0800	[thread overview]
Message-ID: <473A7A0B.5030300@arca.com.cn> (raw)
In-Reply-To: <6934efce0711091131n1acd2ce1h7bb17f9f3cb0f235@mail.gmail.com>


Jared Hulbert a??e??:
> On 10/18/07, Christoph Lameter <clameter@sgi.com> wrote:
>   
>> On Wed, 17 Oct 2007, Jacky(GuangXiang  Lee) wrote:
>>
>>     
>>> seems page migration is used mostly for NUMA platform to improve
>>> performance.
>>> But in a UMA architecture, Is it possible to use page migration to move
>>> pages ?
>>>       
>> Yes. Just one up with a usage for it. The page migration mechanism itself
>> is not NUMA dependent.
>>     
>
> For extreme low power systems it would be possible to shut down banks
> in SDRAM chips that were not full thereby saving power.  That would
> require some defraging and migration to empty them prior to powering
> down those banks.
>
>   
what is the way to shut down banks in SDRAM chips?

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

  parent reply	other threads:[~2007-11-14  4:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 10:19 [PATCH] memory cgroup enhancements [0/5] intro KAMEZAWA Hiroyuki
2007-10-16 10:23 ` [PATCH] memory cgroup enhancements [1/5] force_empty for memory cgroup KAMEZAWA Hiroyuki
2007-10-17  4:17   ` David Rientjes
2007-10-17  5:05     ` Balbir Singh
2007-10-17  5:26       ` KAMEZAWA Hiroyuki
2007-10-17  5:16     ` KAMEZAWA Hiroyuki
2007-10-17  5:38       ` David Rientjes
2007-10-17  5:50         ` KAMEZAWA Hiroyuki
2007-10-17  7:09           ` about page migration on UMA Jacky(GuangXiang  Lee)
2007-10-17  6:44             ` KAMEZAWA Hiroyuki
2007-10-19  1:26             ` Christoph Lameter
2007-11-09 19:31               ` Jared Hulbert
2007-11-09 19:36                 ` Christoph Lameter
2007-11-09 19:54                   ` Jared Hulbert
2007-11-09 19:58                     ` Christoph Lameter
2007-11-09 21:30                       ` Dave Hansen
2007-11-12  0:50                         ` KAMEZAWA Hiroyuki
2007-11-14  4:31                 ` Jacky(GuangXiang Lee) [this message]
2007-11-14 17:05                   ` Jared Hulbert
2007-10-16 10:25 ` [PATCH] memory cgroup enhancements [2/5] remember charge as cache KAMEZAWA Hiroyuki
2007-10-16 10:26 ` [PATCH] memory cgroup enhancements [3/5] record pc is on active list KAMEZAWA Hiroyuki
2007-10-17  4:17   ` David Rientjes
2007-10-17  5:16     ` KAMEZAWA Hiroyuki
2007-10-16 10:27 ` [PATCH] memory cgroup enhancements [4/5] memory cgroup statistics KAMEZAWA Hiroyuki
2007-10-16 10:28 ` [PATCH] memory cgroup enhancements [5/5] show statistics by memory.stat file per cgroup KAMEZAWA Hiroyuki
2007-10-16 18:20 ` [PATCH] memory cgroup enhancements [0/5] intro Balbir Singh
2007-10-16 18:28   ` Andrew Morton
2007-10-16 18:40     ` Balbir Singh
2007-10-17  5:19     ` 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=473A7A0B.5030300@arca.com.cn \
    --to=gxli@arca.com.cn \
    --cc=clameter@sgi.com \
    --cc=climeter@sgi.com \
    --cc=jaredeh@gmail.com \
    --cc=linux-mm@kvack.org \
    /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