All of lore.kernel.org
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Question:  new bind_zonelist uses only one zone type
Date: Tue, 17 Jan 2006 17:46:39 +0900	[thread overview]
Message-ID: <43CCAEEF.5000403@jp.fujitsu.com> (raw)

in -mm4 (in linus.patch)
==
static struct zonelist *bind_zonelist(nodemask_t *nodes)
{
         struct zonelist *zl;
         int num, max, nd;

         max = 1 + MAX_NR_ZONES * nodes_weight(*nodes);
         zl = kmalloc(sizeof(void *) * max, GFP_KERNEL);
         if (!zl)
                 return NULL;
         num = 0;
         for_each_node_mask(nd, *nodes)
                 zl->zones[num++] = &NODE_DATA(nd)->node_zones[policy_zone];
         zl->zones[num] = NULL;
         return zl;
}
==
policy_zone is ZONE_DMA, ZONE_NORMAL, ZONE_HIGHMEM, depends on system.

If policy_zone is ZONE_NORMAL, returned zonelist will be
{Node(0)'s NORMAL, Node(1)'s NORMAL, Node(2)'s Normal.....}

If node0 has only DMA/DMA32 and Node1-NodeX has Normal, node0 will be ignored
and zonelist will include not-populated zone.

Is this intended ?


-- 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-01-17  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  8:46 KAMEZAWA Hiroyuki [this message]
2006-01-17 14:29 ` Question: new bind_zonelist uses only one zone type Andi Kleen
2006-01-17 23:47   ` KAMEZAWA Hiroyuki
2006-01-18  3:00     ` Andi Kleen
2006-01-18  3:26       ` KAMEZAWA Hiroyuki
2006-01-18  3:40       ` Jack Steiner
2006-01-18  3:49         ` Andi Kleen

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=43CCAEEF.5000403@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=clameter@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.