-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'akpm' (patches from Andrew)
Merge updates from Andrew Morton: - a few misc things - ocfs2 updates - most of MM * emailed patches from Andrew Morton <akpm@linux-foundation.org>: (132 commits) hugetlbfs: dirty pages as they are added to pagecache mm: export add_swap_extent() mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS tools/testing/selftests/vm/map_fixed_noreplace.c: add test for MAP_FIXED_NOREPLACE mm: thp: relocate flush_cache_range() in migrate_misplaced_transhuge_page() mm: thp: fix mmu_notifier in migrate_misplaced_transhuge_page() mm: thp: fix MADV_DONTNEED vs migrate_misplaced_transhuge_page race condition mm/kasan/quarantine.c: make quarantine_lock a raw_spinlock_t mm/gup: cache dev_pagemap while pinning pages Revert "x86/e820: put !E820_TYPE_RAM regions into memblock.reserved" mm: return zero_resv_unavail optimization mm: zero remaining unavailable struct pages tools/testing/selftests/vm/gup_benchmark.c: add MAP_HUGETLB option tools/testing/selftests/vm/gup_benchmark.c: add MAP_SHARED option tools/testing/selftests/vm/gup_benchmark.c: allow user specified file tools/testing/selftests/vm/gup_benchmark.c: fix 'write' flag usage mm/gup_benchmark.c: add additional pinning methods mm/gup_benchmark.c: time put_page() mm: don't raise MEMCG_OOM event due to failed high-order allocation mm/page-writeback.c: fix range_cyclic writeback vs writepages deadlock ...
- Loading branch information
Showing
156 changed files
with
3,400 additions
and
1,988 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
================================ | ||
PSI - Pressure Stall Information | ||
================================ | ||
|
||
:Date: April, 2018 | ||
:Author: Johannes Weiner <hannes@cmpxchg.org> | ||
|
||
When CPU, memory or IO devices are contended, workloads experience | ||
latency spikes, throughput losses, and run the risk of OOM kills. | ||
|
||
Without an accurate measure of such contention, users are forced to | ||
either play it safe and under-utilize their hardware resources, or | ||
roll the dice and frequently suffer the disruptions resulting from | ||
excessive overcommit. | ||
|
||
The psi feature identifies and quantifies the disruptions caused by | ||
such resource crunches and the time impact it has on complex workloads | ||
or even entire systems. | ||
|
||
Having an accurate measure of productivity losses caused by resource | ||
scarcity aids users in sizing workloads to hardware--or provisioning | ||
hardware according to workload demand. | ||
|
||
As psi aggregates this information in realtime, systems can be managed | ||
dynamically using techniques such as load shedding, migrating jobs to | ||
other systems or data centers, or strategically pausing or killing low | ||
priority or restartable batch jobs. | ||
|
||
This allows maximizing hardware utilization without sacrificing | ||
workload health or risking major disruptions such as OOM kills. | ||
|
||
Pressure interface | ||
================== | ||
|
||
Pressure information for each resource is exported through the | ||
respective file in /proc/pressure/ -- cpu, memory, and io. | ||
|
||
The format for CPU is as such: | ||
|
||
some avg10=0.00 avg60=0.00 avg300=0.00 total=0 | ||
|
||
and for memory and IO: | ||
|
||
some avg10=0.00 avg60=0.00 avg300=0.00 total=0 | ||
full avg10=0.00 avg60=0.00 avg300=0.00 total=0 | ||
|
||
The "some" line indicates the share of time in which at least some | ||
tasks are stalled on a given resource. | ||
|
||
The "full" line indicates the share of time in which all non-idle | ||
tasks are stalled on a given resource simultaneously. In this state | ||
actual CPU cycles are going to waste, and a workload that spends | ||
extended time in this state is considered to be thrashing. This has | ||
severe impact on performance, and it's useful to distinguish this | ||
situation from a state where some tasks are stalled but the CPU is | ||
still doing productive work. As such, time spent in this subset of the | ||
stall state is tracked separately and exported in the "full" averages. | ||
|
||
The ratios are tracked as recent trends over ten, sixty, and three | ||
hundred second windows, which gives insight into short term events as | ||
well as medium and long term trends. The total absolute stall time is | ||
tracked and exported as well, to allow detection of latency spikes | ||
which wouldn't necessarily make a dent in the time averages, or to | ||
average trends over custom time frames. | ||
|
||
Cgroup2 interface | ||
================= | ||
|
||
In a system with a CONFIG_CGROUP=y kernel and the cgroup2 filesystem | ||
mounted, pressure stall information is also tracked for tasks grouped | ||
into cgroups. Each subdirectory in the cgroupfs mountpoint contains | ||
cpu.pressure, memory.pressure, and io.pressure files; the format is | ||
the same as the /proc/pressure/ files. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.