Searched refs:pressure (Results 1 – 9 of 9) sorted by relevance
18 ConditionPathExists=/proc/pressure/cpu19 ConditionPathExists=/proc/pressure/io20 ConditionPathExists=/proc/pressure/memory
3 Description=Create a lot of memory pressure7 # to throttle and be put under heavy pressure.
3 Description=No memory pressure
3 Description=Test slice for memory pressure kills
3 Description=Create some memory pressure
10 [[ -e /proc/pressure ]] || echo "no PSI" >>/skipped
957 ResourcePressure pressure; in condition_test_psi() local1053 current = &pressure.avg300; in condition_test_psi()1062 current = &pressure.avg10; in condition_test_psi()1064 current = &pressure.avg60; in condition_test_psi()1066 current = &pressure.avg300; in condition_test_psi()1083 r = read_resource_pressure(pressure_path, PRESSURE_TYPE_FULL, &pressure); in condition_test_psi()1085 r = read_resource_pressure(pressure_path, PRESSURE_TYPE_SOME, &pressure); in condition_test_psi()
424 Note that the memory pressure might or might not have been caused by @UNIT@.
739 pressure is above the configured threshold, using the kernel PSI2330 pressure limits before action will be taken, and a new3064 ManagedOOMMemoryPressureLimitPercent= that specify resource pressure3070 or swap pressure is above configured limits. This service is only6786 runtime, speeding up log write performance under pressure. This comes