linux-kernel - Re: [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2

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: <20080321175538.GI2346@one.firstfloor.org>
Date:	Fri, 21 Mar 2008 18:55:38 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <andi@...stfloor.org>, andreas.herrmann3@....com,
	mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2

On Fri, Mar 21, 2008 at 06:41:59PM +0100, Thomas Gleixner wrote:
> On Wed, 12 Mar 2008, Andi Kleen wrote:
> > Add information about the mapping state of the direct mapping to 
> > /proc/meminfo.
> 
> Please use debugfs for this.

But it's not debugging. Or are you saying all memory state information
in /proc/meminfo is debugging information?  I would say it is generic
memory state tracking, similar to VmallocUsed or Slab: or NFS_Unstable:
e.g. I would expect a machine to go slower if all direct mapping pages
are split due to increase TLB misses and that information is generally
useful and should not be forced into some debugging ghetto.

-Andi

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