public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Mel Gorman <mgorman@suse.de>,
	Iulia Manda <iulia.manda21@gmail.com>
Subject: Re: [PATCH 3/3] sched/numa: Fix numabalancing stats in /proc/pid/sched
Date: Thu, 25 Jun 2015 13:40:21 -0400	[thread overview]
Message-ID: <558C3D05.4070701@redhat.com> (raw)
In-Reply-To: <1435252903-1081-4-git-send-email-srikar@linux.vnet.ibm.com>

On 06/25/2015 01:21 PM, Srikar Dronamraju wrote:
> Commit 44dba3d5d6a1 (sched: Refactor task_struct to use numa_faults
> instead of numa_* pointers) modified the way tsk->numa_faults stats are
> accounted. However that commit never touched show_numa_stats() that
> displays /proc/pid/sched. Now the numbers displayed in /proc/pid/sched
> dont match the actual numbers.
> 
> Fix it by making sure that /proc/pid/sched reflects the task fault numbers
> Also add group fault stats too.
> 
> Also couple of more modifications are added here.
> 1. Format change.
> - Previously we would list two entries per node, one for private and one for
>   shared. Also the home node info was listed in each entry.
> 
> - Now preferred node, total_faults and current node are displayed separately.
> - Now there is one entry per node, that lists private,shared task and group
>   faults.
> 
> 2. p->numa_pages_migrated was getting reset after every read of
>    /proc/pid/sched. Its more useful to have absolute numbers since
>    differential migrations between two accesses can be easily calculated.
> 
> Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>

Acked-by: Rik van Riel <riel@redhat.com>


Thank you for updating the statistics to match what
the code does nowadays.


  reply	other threads:[~2015-06-25 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 17:21 [PATCH 0/3] sched/numa: Update numa_balancing stats in /proc Srikar Dronamraju
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 [this message]
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=558C3D05.4070701@redhat.com \
    --to=riel@redhat.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=srikar@linux.vnet.ibm.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