linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
	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: Tue, 23 Sep 2008 20:46:56 +0100	[thread overview]
Message-ID: <20080923194655.GA25542@csn.ul.ie> (raw)
In-Reply-To: <20080923211140.DC16.KOSAKI.MOTOHIRO@jp.fujitsu.com>

On (23/09/08 21:15), KOSAKI Motohiro didst pronounce:
> > > The corollary is that someone running with a 64K base page kernel may be
> > > surprised that the pagesize is always 4K. However I'll check if there is
> > > a simple way of checking out if the MMU size differs from PAGE_SIZE.
> > 
> > Sure.  If it isn't easy, the best thing to do is probably just to
> > document the "interesting" behavior.
> 
> Dave, please let me know getpagesize() function return to 4k or 64k on ppc64.
> I think the PageSize line of the /proc/pid/smap and getpagesize() result should be matched.
> 
> otherwise, enduser may be confused.
> 

To distinguish between the two, I now report the kernel pagesize and the
mmu pagesize like so

KernelPageSize:       64 kB
MMUPageSize:           4 kB

This is running a kernel with a 64K base pagesize on a PPC970MP which
does not support 64K hardware pagesizes.

Does this make sense?

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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>

  reply	other threads:[~2008-09-23 19:46 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
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 [this message]
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=20080923194655.GA25542@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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