linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Nathan Lynch <nathanl@linux.ibm.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	Mingming Cao <mingming.cao@ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/8] Provide vcpu dispatch statistics
Date: Fri, 10 May 2019 21:56:15 +0530	[thread overview]
Message-ID: <cover.1557502887.git.naveen.n.rao@linux.vnet.ibm.com> (raw)

This series adds a new procfs file /proc/powerpc/vcpudispatch_stats for 
providing statistics around how the LPAR processors are dispatched by 
the POWER Hypervisor, in a shared LPAR environment. Patch 6/8 has more 
details on how the statistics are gathered.

An example output:
    $ sudo cat /proc/powerpc/vcpudispatch_stats
    cpu0 6839 4126 2683 30 0 6821 18 0
    cpu1 2515 1274 1229 12 0 2509 6 0
    cpu2 2317 1198 1109 10 0 2312 5 0
    cpu3 2259 1165 1088 6 0 2256 3 0
    cpu4 2205 1143 1056 6 0 2202 3 0
    cpu5 2165 1121 1038 6 0 2162 3 0
    cpu6 2183 1127 1050 6 0 2180 3 0
    cpu7 2193 1133 1052 8 0 2187 6 0
    cpu8 2165 1115 1032 18 0 2156 9 0
    cpu9 2301 1252 1033 16 0 2293 8 0
    cpu10 2197 1138 1041 18 0 2187 10 0
    cpu11 2273 1185 1062 26 0 2260 13 0
    cpu12 2186 1125 1043 18 0 2177 9 0
    cpu13 2161 1115 1030 16 0 2153 8 0
    cpu14 2206 1153 1033 20 0 2196 10 0
    cpu15 2163 1115 1032 16 0 2155 8 0

In the output above, for vcpu0, there have been 6839 dispatches since
statistics were enabled. 4126 of those dispatches were on the same
physical cpu as the last time. 2683 were on a different core, but within
the same chip, while 30 dispatches were on a different chip compared to
its last dispatch.

Also, out of the total of 6839 dispatches, we see that there have been
6821 dispatches on the vcpu's home node, while 18 dispatches were
outside its home node, on a neighbouring chip.

Changes since RFC:
- Patches 1/8 to 5/8: no changes, except rebase to powerpc/merge
- Patch 6/8: The mutex guarding the vphn hcall has been dropped. It was 
  only meant to serialize hcalls issued when stats are initially 
  enabled.  However, in reality, the various per-cpu workers will be 
  scheduled at slightly different times and chances of hcalls for 
  retrieving the same associativity information at the same time is very 
  less. Even in that case, there are no other side effects.
- Patch 6/8: The third column for vcpu dispatches on the same core, but 
  different thread has been dropped and merged with the second column.  
- Patch 7/8: new patch to ensure we don't take too much time while 
  enabling/disabling statistics on large systems with heavy workload.
- Patch 8/8: new patch adding a document describing the fields in the 
  procfs file.


- Naveen

Naveen N. Rao (8):
  powerpc/pseries: Use macros for referring to the DTL enable mask
  powerpc/pseries: Do not save the previous DTL mask value
  powerpc/pseries: Factor out DTL buffer allocation and registration
    routines
  powerpc/pseries: Generalize hcall_vphn()
  powerpc/pseries: Introduce helpers to gatekeep DTLB usage
  powerpc/pseries: Provide vcpu dispatch statistics
  powerpc/pseries: Protect against hogging the cpu while setting up the
    stats
  powerpc/pseries: Add documentation for vcpudispatch_stats

 Documentation/powerpc/vcpudispatch_stats.txt |  68 +++
 arch/powerpc/include/asm/lppaca.h            |  11 +
 arch/powerpc/include/asm/plpar_wrappers.h    |   4 +
 arch/powerpc/include/asm/topology.h          |   4 +
 arch/powerpc/mm/book3s64/vphn.h              |   8 +
 arch/powerpc/mm/numa.c                       | 134 ++++-
 arch/powerpc/platforms/pseries/dtl.c         |  22 +-
 arch/powerpc/platforms/pseries/lpar.c        | 550 ++++++++++++++++++-
 arch/powerpc/platforms/pseries/setup.c       |  34 +-
 9 files changed, 760 insertions(+), 75 deletions(-)
 create mode 100644 Documentation/powerpc/vcpudispatch_stats.txt

-- 
2.21.0


             reply	other threads:[~2019-05-10 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 16:26 Naveen N. Rao [this message]
2019-05-10 16:26 ` [PATCH 1/8] powerpc/pseries: Use macros for referring to the DTL enable mask Naveen N. Rao
2019-05-13 14:55   ` Nathan Lynch
2019-05-10 16:26 ` [PATCH 2/8] powerpc/pseries: Do not save the previous DTL mask value Naveen N. Rao
2019-05-13 16:29   ` Nathan Lynch
2019-05-10 16:26 ` [PATCH 3/8] powerpc/pseries: Factor out DTL buffer allocation and registration routines Naveen N. Rao
2019-05-10 16:26 ` [PATCH 4/8] powerpc/pseries: Generalize hcall_vphn() Naveen N. Rao
2019-05-10 16:26 ` [PATCH 5/8] powerpc/pseries: Introduce helpers to gatekeep DTLB usage Naveen N. Rao
2019-05-10 16:26 ` [PATCH 6/8] powerpc/pseries: Provide vcpu dispatch statistics Naveen N. Rao
2019-05-10 16:26 ` [PATCH 7/8] powerpc/pseries: Protect against hogging the cpu while setting up the stats Naveen N. Rao
2019-05-10 16:26 ` [PATCH 8/8] powerpc/pseries: Add documentation for vcpudispatch_stats Naveen N. Rao

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=cover.1557502887.git.naveen.n.rao@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingming.cao@ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=nathanl@linux.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;
as well as URLs for NNTP newsgroup(s).