[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1FE6DD409037234FAB833C420AA843ECF9DFC4@orsmsx424.amr.corp.intel.com>
Date: Wed, 2 Apr 2008 14:53:45 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: "Johannes Weiner" <hannes@...urebad.de>,
<linux-kernel@...r.kernel.org>
Cc: <linux-mm@...ck.org>, <mingo@...e.hu>, <davem@...emloft.net>,
<hskinnemoen@...el.com>, <cooloney@...nel.org>, <starvik@...s.com>,
<dhowells@...hat.com>, <ysato@...rs.sf.net>,
<takata@...ux-m32r.org>, <geert@...ux-m68k.org>,
<ralf@...ux-mips.org>, <kyle@...isc-linux.org>, <paulus@...ba.org>,
<schwidefsky@...ibm.com>, <lethal@...ux-sh.org>,
<jdike@...toit.com>, <miles@....org>, <chris@...kel.net>,
<rmk@....linux.org.uk>
Subject: RE: [RFC 00/21] Generic show_mem()
> Tony, as far as I understand, ia64 jumps holes in the memory map with
> vmemmap_find_next_valid_pfn(). Any idea if and how this could be
> built into the generic show_mem() version?
Perhaps it might be worth looking at this when ia64 slims down to
just one memory model (using sparse virtual mem map). But I don't
think anyone is actively working on this. Right now we have two
very different show_mem() functions for the contig and discontig
cases.
This whole function sends shivers down my spine for a large
system though ... that inner loop looks at every single page
structure ... on a multi-terabyte machine that could run to
billions of cache misses. Hope the users aren't in a hurry
to see the answer ... or doing something painful like:
# watch -n 1 cat /proc/meminfo
-Tony
--
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