From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
agl@us.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: Wed, 24 Sep 2008 11:59:09 -0700 [thread overview]
Message-ID: <1222282749.15523.59.camel@nimitz> (raw)
In-Reply-To: <20080924171003.GD10837@csn.ul.ie>
On Wed, 2008-09-24 at 18:10 +0100, Mel Gorman wrote:
> On (24/09/08 09:06), Dave Hansen didst pronounce:
> > On Wed, 2008-09-24 at 16:41 +0100, Mel Gorman wrote:
> > > I admit it's ppc64-specific. In the latest patch series, I made this a
> > > separate patch so that it could be readily dropped again for this reason.
> > > Maybe an alternative would be to display MMUPageSize *only* where it differs
> > > from KernelPageSize. Would that be better or similarly confusing?
> >
> > I would also think that any arch implementing fallback from large to
> > small pages in a hugetlbfs area (Adam needs to post his patches :) would
> > also use this.
> >
>
> Fair point. Maybe the thing to do is backburner this patch for the moment and
> reintroduce it when/if an architecture supports demotion? The KernelPageSize
> reporting in smaps and what the hpagesize in maps is still useful though
> I believe. Any comment?
I'd kinda prefer to see it normalized into a single place rather than
sprinkle it in each smaps file. We should be able to figure out which
mount the file is from and, from there, maybe we need some per-mount
information exported.
> (future stuff from here on)
>
> In the future if demotion does happen then the MMUPageSize information may
> be genuinely useful instead of just a curious oddity on ppc64. As you point
> out, Adam (added to cc) has worked on this area (starting with x86 demotion)
> in the past but it's a while before it'll be considered for merging I believe.
>
> That aside, more would need to be done with the page size reporting then
> anyway. For example, it maybe indicate how much of each pagesize is in a VMA
> or indicate that KernelPageSize is what is being requested but in reality
> it is mixed like;
>
> KernelPageSize: 2048 kB (mixed)
>
> or
>
> KernelPageSize: 2048 kB * 5, 4096 kB * 20
Looks a bit verbose, but I agree with the sentiment.
-- 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>
next prev parent reply other threads:[~2008-09-24 18:59 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
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 [this message]
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=1222282749.15523.59.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=agl@us.ibm.com \
--cc=kosaki.motohiro@jp.fujitsu.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