Messages in this thread | | | Date | Thu, 9 Oct 2008 01:38:31 +0400 | From | Alexey Dobriyan <> | Subject | Re: [PATCH 1/2] Report the pagesize backing a VMA in /proc/pid/smaps |
| |
On Fri, Oct 03, 2008 at 05:46:54PM +0100, Mel Gorman wrote: > It is useful to verify a hugepage-aware application is using the expected > pagesizes for its memory regions. This patch creates an entry called > KernelPageSize in /proc/pid/smaps that is the size of page used by the > kernel to back a VMA. The entry is not called PageSize as it is possible > the MMU uses a different size. This extension should not break any sensible > parser that skips lines containing unrecognised information.
> + "KernelPageSize: %8lu kB\n",
> +unsigned long vma_kernel_pagesize(struct vm_area_struct *vma) > +{ > + struct hstate *hstate; > + > + if (!is_vm_hugetlb_page(vma)) > + return PAGE_SIZE; > + > + hstate = hstate_vma(vma); > + VM_BUG_ON(!hstate); > + > + return 1UL << (hstate->order + PAGE_SHIFT); ^^^^ VM_BUG_ON is unneeded because kernel will oops here if hstate is NULL.
Also, in /proc/*/maps it's printed only for hugetlb vmas and called hpagesize, in smaps it's printed for every vma and called KernelPageSize. All of this is inconsistent.
And app will verify once that hugepages are of right size, so Pss cost argument for changing /proc/*/maps seems weak to me.
| |