Re: [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
- Date: Fri, 21 Mar 2008 18:55:38 +0100
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- [PATCH] CPA: Add statistics about state of direct mapping v3
- From: Andi Kleen
- [PATCH] CPA: Add statistics about state of direct mapping v3
- References:
- [PATCH] [1/7] Implement true end_pfn_mapped for 32bit
- From: Andi Kleen
- [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2
- From: Andi Kleen
- Re: [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2
- From: Thomas Gleixner
- [PATCH] [1/7] Implement true end_pfn_mapped for 32bit
- Prev by Date: Re: fglrx
- Next by Date: Re: [PATCH] [6/7] Split large page mapping for AMD TSEG
- Previous by thread: Re: [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2
- Next by thread: [PATCH] CPA: Add statistics about state of direct mapping v3
- Index(es):
Relevant Pages
|
