optionally sync per-CPU vmstats counter on return to userspace
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 13 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | sched: isolation: introduce vmstat_sync isolcpu flagsDocumentation/ include/ kernel/ | +24 | 0 replies | |
| 2/5 | common entry: add hook for isolation to __syscall_exit_to_user_mode_workkernel/ | +9 | 0 replies | |
| 3/5 | mm: vmstat: optionally flush per-CPU vmstat counters on return to userspaceinclude/ kernel/ kernel/ +1 more | +68 | 0 replies | |
| 4/5 | mm: vmstat: move need_updatemm/ | +34 | 0 replies | |
| 5/5 | mm: vmstat_refresh: avoid queueing work item if cpu stats are cleanmm/ | +34 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 0/5] optionally sync per-CPU vmstats counter on return to userspace
The logic to disable vmstat worker thread, when entering nohz full, does not cover all scenarios. For example, it is possible for the following to happen:
1) enter nohz_full, which calls refresh_cpu_vm_stats, syncing the stats.
2) app runs mlock, which increases counters for mlock'ed pages.
3) start -RT loop
Since refresh_cpu_vm_stats from nohz_full logic can happen _before_ the mlock, vmstat shepherd can restart vmstat worker thread on the CPU in question.
To fix this, optionally sync the vmstat counters when returning from userspace, controllable by a new "vmstat_sync" isolcpus flags (default off).
See individual patches for details.