linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@engr.sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] pearing off zone from physical memory layout [0/10]
Date: Fri, 3 Feb 2006 08:47:42 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0602030842310.386@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <43E307DB.3000903@jp.fujitsu.com>

On Fri, 3 Feb 2006, KAMEZAWA Hiroyuki wrote:

> By this, zone's meaning will be changed from "a range of memory to be used
> in a same manner" to "a group of memory to be used in a same manner".

For us on IA64 a zone describes the memory of a node in a NUMA system. 
This is due to our IA64 not having memory issues like restricted DMA 
areas or not directly addressable memory.

That memory is to be used in the same manner. Yes. So in principle this 
would also work for us. I'd like to have an option though to get rid of 
all the extra zones if one has a clean memory architecture. We still carry 
the DMA and HIGHMEM stuff around without purpose.

Would this also mean that one can dynamically add/remove memory to a zone 
if the memory has to be treated the same way?


--
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:[~2006-02-03 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  7:35 KAMEZAWA Hiroyuki
2006-02-03 16:47 ` Christoph Lameter [this message]
2006-02-03 17:02   ` Kamezawa Hiroyuki
2006-02-06 19:27 ` Dave Hansen
2006-02-06 23:59   ` 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.62.0602030842310.386@schroedinger.engr.sgi.com \
    --to=clameter@engr.sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.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