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