linux-kernel - Re: [PATCH] x86: fix /proc/meminfo DirectMap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0808151426080.309@blonde.site>
Date:	Fri, 15 Aug 2008 14:32:15 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Ingo Molnar <mingo@...e.hu>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: fix /proc/meminfo DirectMap

On Fri, 15 Aug 2008, Andi Kleen wrote:
> 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.

Yes, that's what I meant by the TLB optimizers.  But it's going to
be a fractional effect, isn't it, when you're trying to get the last
1% out of the machine?  And in such a case, you might wonder more
what all the 4k ones are actually being used for (no problem at all
if they've ended up behind vmalloced module text).

Hugh
--
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/