On Mon, 20 Oct 2014, David Rientjes <[email protected]> wrote: > On Tue, 21 Oct 2014, Petr Holasek wrote: > > > There were some similar attempts to add vma's pagesize to numa_maps in the > > past, > > so I've distilled the most straightforward one - adding pagesize field > > expressing size in kbytes to each line. Although page size can be also > > obtained > > from smaps file, adding pagesize to numa_maps makes the interface more > > compact > > and easier to use without need for traversing other files. > > > > New numa_maps output looks like that: > > > > 2aaaaac00000 default file=/dev/hugepages/hugepagefile huge pagesize=2097152 > > dirty=1 N0=1 > > 7f302441a000 default file=/usr/lib64/libc-2.17.so pagesize=4096 mapped=65 > > mapmax=38 N0=65 > > > > Signed-off-by: Petr Holasek <[email protected]> > > I guess the existing "huge" is insufficient on platforms that support > multiple hugepage sizes.
Why do you think so? pagesize= could also distinguish between multiple hugepage sizes. -- Petr Holasek [email protected] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
