Lines Matching +full:stretch +full:- +full:updates
8 ## Per-process polled counters
11 `/proc/<pid>/oom_score_adj` at user-defined intervals.
13 See [`man 5 proc`][man-proc] for their semantic.
28 ---|--------------|----------|-----------|----
42 [ProcessStats reference](/docs/reference/trace-packet-proto.autogen#ProcessStats).
56 ## Per-process memory events (ftrace)
63 being an event-driven push event it allows to detect very short memory usage
72 since Linux v5.5-rc1. This patch has been backported in several Google Pixel
81 (a subset of the ones exposed by `/proc/vmstat`). Unlike RSS-stat counter
82 updates, mm events are extremely high volume and tracing them individually would
123 ---|-------|--------------|-----------|----
151 ## System-wide polled counters
155 - `/proc/stat`
156 - `/proc/vmstat`
157 - `/proc/meminfo`
159 See [`man 5 proc`][man-proc] for their semantic.
175 ---|------|---------
186 [TraceConfig reference](/docs/reference/trace-config-proto.autogen#SysStatsConfig)
214 ## Low-memory Kills (LMK)
231 A LMK of a cached app or service, instead, is frequently business-as-usual and
233 the app, which will then cold-start.
237 that most processes get LMK-ed in a short time frame) and are often the symptom
242 #### In-kernel lowmemorykiller driver
243 In Android, LMK used to be handled by an ad-hoc kernel-driver,
252 necessarily use `lmkd` as the ultimate choice of in-kernel vs userspace is
255 On Google Pixel phones, `lmkd`-side killing is used since Pixel 2 running
264 LMKs on Android, whether the old in-kernel `lowmemkiller` or the newer `lmkd`,
266 [Linux kernel's OOM Killer](https://linux-mm.org/OOM_Killer).
267 Perfetto at the moment supports only Android LMK events (Both in-kernel and
268 user-space) and does not support tracing of Linux kernel OOM Killer events.
271 mis-configured BSP.
285 Both newer lmkd and legacy kernel-driven lowmemorykiller events are normalized
297 |----|------|-----|
311 # For old in-kernel events.
325 ## {#oom-adj} App states and OOM adjustment score
333 …st sources](https://cs.android.com/android/platform/superproject/+/android10-release:frameworks/ba…
346 // The B list of SERVICE_ADJ -- these are the old and decrepit
354 // UI flow such as clicking on a URI in the e-mail app to view in the browser,
355 // and then pressing back to return to e-mail.
358 // This is a process holding the home application -- we want to try
363 // This is a process holding an application service -- killing it will not
367 // This is a process with a heavy-weight application. It is in the
400 static final int PERSISTENT_SERVICE_ADJ = -700;
404 static final int PERSISTENT_PROC_ADJ = -800;
407 static final int SYSTEM_ADJ = -900;
411 static final int NATIVE_ADJ = -1000;
414 [man-proc]: https://manpages.debian.org/stretch/manpages/proc.5.en.html