linux-kernel - Re: [RFC][PATCH] show page size in /proc/$pid/numa

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] [day] [month] [year] [list]

Date:	Fri, 23 Sep 2011 13:04:12 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Dave Hansen <dave@...ux.vnet.ibm.com>
cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] show page size in /proc/$pid/numa_maps

On Fri, 23 Sep 2011, Dave Hansen wrote:

> > Why not just add a pagesize={4K,2M,1G,...} field for every output? 
> 
> I think it's a bit misleading.  With THP at least we have 2M pages in
> the MMU, but we're reporting in 4k units.
> 
> I certainly considered doing just what you're suggesting, though.  It's
> definitely not a bad idea.  Certainly much more clear.
> 

Een though the code is in task_mmu.c, I think that /proc/pid/numa_maps 
should be more representative of the state of vmas where any 
pagesize={4K,2M,1G,...} would be true rather than whether or not the mmu 
sees tham as large or small pages.  I actually don't see much difference 
between anon=50 pagemult=512 and anon=50 pagesize=2M, but I'd definitely 
recommend printing the field for every vma.
--
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/