linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] Report the pagesize backing a VMA in /proc/pid/smaps
Date: Mon, 22 Sep 2008 08:55:55 -0700	[thread overview]
Message-ID: <1222098955.8533.50.camel@nimitz> (raw)
In-Reply-To: <1222047492-27622-2-git-send-email-mel@csn.ul.ie>

On Mon, 2008-09-22 at 02:38 +0100, Mel Gorman wrote:
> It is useful to verify that a hugepage-aware application is using the expected
> pagesizes in each of its memory regions. This patch reports the pagesize
> backing the VMA in /proc/pid/smaps. This should not break any sensible
> parser as the file format is multi-line and it should skip information it
> does not recognise.

Time to play devil's advocate. :)

To be fair, this doesn't return the MMU pagesize backing the VMA.  It
returns pagesize that hugetlb reports *or* the kernel's base PAGE_SIZE.

The ppc64 case where we have a 64k PAGE_SIZE, but no hardware 64k
support means that we'll have a 4k MMU pagesize that we're pretending is
a 64k MMU page.  That might confuse someone seeing 16x the number of TLB
misses they expect.

This also doesn't work if, in the future, we get multiple page sizes
mapped under one VMA.  But, I guess that all only matters if you worry
about how the kernel is treating the pages vs. the MMU hardware.

-- Dave

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-09-22 15:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22  1:38 [PATCH 0/2] Report the pagesize backing VMAs in /proc Mel Gorman
2008-09-22  1:38 ` [PATCH 1/2] Report the pagesize backing a VMA in /proc/pid/smaps Mel Gorman
2008-09-22  8:30   ` Andrew Morton
2008-09-22 16:17     ` Mel Gorman
2008-09-22 15:55   ` Dave Hansen [this message]
2008-09-22 16:21     ` Mel Gorman
2008-09-22 16:48       ` Dave Hansen
2008-09-23 12:15         ` KOSAKI Motohiro
2008-09-23 19:46           ` Mel Gorman
2008-09-24 12:32             ` KOSAKI Motohiro
2008-09-24 15:41               ` Mel Gorman
2008-09-24 16:06                 ` Dave Hansen
2008-09-24 17:10                   ` Mel Gorman
2008-09-24 18:59                     ` Dave Hansen
2008-09-24 19:11                       ` Mel Gorman
2008-09-24 19:23                         ` Dave Hansen
2008-09-24 23:39                           ` Mel Gorman
2008-09-24 23:42                           ` Mel Gorman
2008-09-25 12:23                 ` KOSAKI Motohiro
2008-09-22  1:38 ` [PATCH 2/2] Report the pagesize backing a VMA in /proc/pid/maps Mel Gorman
2008-10-03 16:46 [PATCH 0/2] Report the size of pages backing VMAs in /proc V3 Mel Gorman
2008-10-03 16:46 ` [PATCH 1/2] Report the pagesize backing a VMA in /proc/pid/smaps Mel Gorman
2008-10-08 21:38   ` Alexey Dobriyan
2008-10-09  2:16     ` KOSAKI Motohiro
2008-10-09 10:24     ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1222098955.8533.50.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox