[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080602160548.B6D4.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date: Mon, 02 Jun 2008 16:09:18 +0900
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Eric Dumazet <dada1@...mosbay.com>
Cc: kosaki.motohiro@...fujitsu.com,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <clameter@....com>,
Nick Piggin <nickpiggin@...oo.com.au>,
Hugh Dickins <hugh@...itas.com>,
linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] vmallocinfo: Add NUMA informations
Hi
> Christoph recently added /proc/vmallocinfo file to get information about
> vmalloc allocations.
>
> This patch adds NUMA specific information, giving number of pages
> allocated on each memory node.
>
> This should help to check that vmalloc() is able to respect NUMA policies.
good patch :)
> +static void show_numa_infos(struct seq_file *m, struct vm_struct *v)
> +{
> + if (NUMA_BUILD) {
> + unsigned int *counters, nr;
> +
> + counters = kzalloc(MAX_NUMNODES * sizeof(unsigned int),
> + GFP_KERNEL);
> + if (!counters)
> + return;
> +
> + for (nr = 0; nr < v->nr_pages; nr++)
> + counters[page_to_nid(v->pages[nr])]++;
> +
> + for (nr = 0; nr < MAX_NUMNODES; nr++)
> + if (counters[nr])
> + seq_printf(m, " N%u=%u", nr, counters[nr]);
> +
for_each_node_state(n, N_HIGH_MEMORY) is better?
because MAX_NUMNODES has offten very large value.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists