All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] pearing off zone from physical memory layout [0/10]
Date: Sat, 04 Feb 2006 02:02:18 +0900	[thread overview]
Message-ID: <43E38C9A.7060103@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0602030842310.386@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> 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.
> 
Unfortunately, some of ia64 machines has DMA zone (for support 32bit bus < 4G mem).
But yes, HIGHMEM is not necessary.

> Would this also mean that one can dynamically add/remove memory to a zone 
> if the memory has to be treated the same way?
> 
Yes, I think so.  When support buddy-system, it can be done by MAX_ORDER size.
One of my purpose is to add memory to NORMAL if necessary.
(removing looks difficult ?)

Thanks,
-- Kame

--
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 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  7:35 [RFC] pearing off zone from physical memory layout [0/10] KAMEZAWA Hiroyuki
2006-02-03 16:47 ` Christoph Lameter
2006-02-03 17:02   ` Kamezawa Hiroyuki [this message]
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=43E38C9A.7060103@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=clameter@engr.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.