From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, srikar@linux.vnet.ibm.com,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
Iulia Manda <iulia.manda21@gmail.com>
Subject: [PATCH 0/3] sched/numa: Update numa_balancing stats in /proc
Date: Thu, 25 Jun 2015 22:51:40 +0530 [thread overview]
Message-ID: <1435252903-1081-1-git-send-email-srikar@linux.vnet.ibm.com> (raw)
Recent changes to numa balancing like adding group faults, merging
numa_faults and numa_mem_faults have not been reflected in /proc.
Hence some of the numa_balancing information is not exposed or displays
wrong info. This patchset tries to correct it.
Before change: /proc/pid/sched
clock-delta : 12
mm->numa_scan_seq : 34
numa_migrations, 1
numa_faults_memory, 0, 0, 1, 0, -1
numa_faults_memory, 1, 0, 0, 0, -1
numa_faults_memory, 0, 1, 0, 0, -1
numa_faults_memory, 1, 1, 0, 0, -1
numa_faults_memory, 0, 2, 0, 0, -1
numa_faults_memory, 1, 2, 0, 0, -1
numa_faults_memory, 0, 3, 0, 0, -1
numa_faults_memory, 1, 3, 0, 0, -1
After change: /proc/pid/sched
clock-delta : 12
mm->numa_scan_seq : 34
numa_pages_migrated : 1
numa_preferred_nid : 0
total_numa_faults : 2627
current_node=0, numa_group_id=6958
numa_faults node=0 task_private=1344 task_shared=0 group_private=1344 group_shared=0
numa_faults node=1 task_private=641 task_shared=65 group_private=641 group_shared=65
numa_faults node=2 task_private=512 task_shared=0 group_private=512 group_shared=0
numa_faults node=3 task_private=64 task_shared=1 group_private=64 group_shared=1
Srikar Dronamraju (3):
sched: Move print_cfs_rq declaration to kernel/sched/sched.h
sched/numa: Show numa_group id in sched_debug task listings
sched/numa: Fix numabalancing stats in /proc/pid/sched
include/linux/sched.h | 2 --
kernel/sched/debug.c | 40 ++++++++++++++++++----------------------
kernel/sched/fair.c | 22 +++++++++++++++++++++-
kernel/sched/sched.h | 13 +++++++++++++
4 files changed, 52 insertions(+), 25 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-06-25 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 17:21 Srikar Dronamraju [this message]
2015-06-25 17:21 ` [PATCH 1/3] sched: Move print_cfs_rq declaration to kernel/sched/sched.h Srikar Dronamraju
2015-06-25 17:39 ` Rik van Riel
2015-07-03 7:46 ` [tip:sched/urgent] sched/debug: Move print_cfs_rq() " tip-bot for Srikar Dronamraju
2015-07-04 8:07 ` tip-bot for Srikar Dronamraju
2015-06-25 17:21 ` [PATCH 2/3] sched/numa: Show numa_group id in sched_debug task listings Srikar Dronamraju
2015-06-25 17:39 ` Rik van Riel
2015-07-03 7:47 ` [tip:sched/urgent] sched/numa: Show numa_group ID in /proc/ " tip-bot for Srikar Dronamraju
2015-07-04 8:07 ` tip-bot for Srikar Dronamraju
2015-06-25 17:21 ` [PATCH 3/3] sched/numa: Fix numabalancing stats in /proc/pid/sched Srikar Dronamraju
2015-06-25 17:40 ` Rik van Riel
2015-07-03 7:47 ` [tip:sched/urgent] sched/numa: Fix numa balancing stats in /proc/ pid/sched tip-bot for Srikar Dronamraju
2015-07-04 8:08 ` tip-bot for Srikar Dronamraju
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=1435252903-1081-1-git-send-email-srikar@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=iulia.manda21@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@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
all inboxes | Powered by JetHome®