From: David Rientjes <rientjes@google.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Rafael Aquini <aquini@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
oleg@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH] proc: task_mmu: show page size in /proc/<pid>/numa_maps
Date: Mon, 22 Dec 2014 14:27:39 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1412221422120.11431@chino.kir.corp.google.com> (raw)
In-Reply-To: <5495A698.4050707@linux.intel.com>
On Sat, 20 Dec 2014, Dave Hansen wrote:
> I sometimes wonder what 'numa_maps' purpose is any if we should have
> _some_ kind of policy about what goes in there vs. smaps. numa_maps
> seems to be turning in to smaps, minus the \n. :)
>
It seems like an interface, similar to the one proposed by Ulrich, that
described the NUMA topology would have obsoleted numa_maps and you could
only rely on smaps to determine locality. There's existing userspace
dependencies on numa_maps already, though, so owell.
I had to fix numa_maps output when autonuma was merged for a much more
subtle difference at
http://marc.info/?l=git-commits-head&m=139113691614467 so I know some
people actually parse this and care quite a bit about its accuracy, it's a
shame it can't be deprecated in favor of adding the necessary information
to smaps.
--
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:[~2014-12-22 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 13:54 Rafael Aquini
2014-12-20 16:40 ` Dave Hansen
2014-12-22 22:27 ` David Rientjes [this message]
2014-12-20 18:36 ` Johannes Weiner
2014-12-20 19:44 ` Rafael Aquini
2014-12-21 18:02 ` Dave Hansen
2014-12-21 22:28 ` Rafael Aquini
2014-12-22 17:10 ` Dave Hansen
2014-12-22 17:25 ` Rafael Aquini
2014-12-22 17:59 ` Dave Hansen
2014-12-22 22:21 ` David Rientjes
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=alpine.DEB.2.10.1412221422120.11431@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
/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