Re: [PATCH] x86: fix /proc/meminfo DirectMap

[Andi Kleen]

On Fri, Aug 15, 2008 at 01:58:32PM +0100, Hugh Dickins wrote:
> Do we actually want these DirectMap lines in the x86 /proc/meminfo?
> I can see they're interesting to CPA developers and TLB optimizers,
> but they don't fit its usual "where has all my memory gone?" usage.

It was intended for the "why is my computer going slower" usage.

> If they are to stay, here are some fixes.
> 
> 1. On x86_32 without PAE, they're not 2M but 4M pages: no need to
>    mess with the internal enum, but show the right name to users.
> 
> 2. Many machines can never show anything but 0 for DirectMap1G,
>    so suppress that line unless direct_gbpages are really enabled.

I made them unconditional to minimize the risk of some dumb
parser not being able to deal with them. Longer term there
will be more and more machines that support them.

Admittedly that's not a very strong argument.

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/