Searched refs:oom (Results 1 - 25 of 51) sorted by last modified time

123

/linux-master/tools/testing/selftests/cgroup/
H A D	test_memcontrol.c	5 #include <linux/oom.h> 418 long low, oom; local 420 oom = cg_read_key_long(children[i], "memory.events", "oom "); 423 if (oom) 859 if (cg_read_key_long(memcg, "memory.events", "oom ") != 1) 883 * up to OOM. Then it checks for oom and oom_kill events in 910 if (cg_read_key_long(memcg, "memory.events", "oom ") != 1) 1113 * up to OOM with memory.group.oom set. Then it checks that all 1144 if (cg_write(child, "memory.oom [all...]
/linux-master/mm/
H A D	swapfile.c	37 #include <linux/oom.h>
H A D	vmscan.c	46 #include <linux/oom.h>
H A D	page_ext.c	487 goto oom; 496 oom:
H A D	page_alloc.c	30 #include <linux/oom.h> 42 #include <trace/events/oom.h> 3520 * Acquire the oom lock. If that fails, somebody else is 3531 * here, this is only to catch a parallel oom killing, we must fail if 3747 * inside the allocator rather than hit the oom killer prematurely. 3979 * !MMU doesn't have oom reaper so give access to memory reserves 3990 * reserves from oom victims which can live with a portion of it 4023 * Returns true if a retry is viable or false to enter the oom path.
H A D	oom_kill.c	21 #include <linux/oom.h> 54 #include <trace/events/oom.h> 61 * Serializes oom killer invocations (out_of_memory()) from all contexts to 62 * prevent from over eager oom killing (e.g. when the oom killer is invoked 87 * This function is assuming oom-killer context and 'current' has triggered 88 * the oom-killer. 101 * If this is a mempolicy constrained oom, tsk's 109 * This is not a mempolicy constrained oom, so only 154 * order == -1 means the oom kil [all...]
H A D	mmap.c	47 #include <linux/oom.h> 3316 * Set MMF_OOM_SKIP to hide this task from the oom killer/reaper
H A D	migrate_device.c	13 #include <linux/oom.h>
H A D	migrate.c	48 #include <linux/oom.h>
H A D	memory.c	75 #include <linux/oom.h> 3293 goto oom; 3410 oom: 4465 goto oom; 4526 oom:
H A D	memcontrol.c	61 #include <linux/oom.h> 2181 * relying on the oom victim to make a forward progress and we can 2182 * invoke the oom killer here. 2298 * In this case it's better to ignore memory.group.oom. 2306 * highest-level memory cgroup with oom.group set. 2328 pr_cont(" are going to be killed due to memory.oom.group set\n"); 2827 * subsequent retries we only want to do what's necessary to prevent oom 2983 /* Avoid endless loop for tasks bypassed by the oom killer */ 2988 * keep retrying as long as the memcg oom killer is able to make 2989 * a forward progress or bypass the charge if the oom kille [all...]
H A D	ksm.c	41 #include <linux/oom.h> 705 * just to undo a merge it made a moment before, so unlikely to oom.
H A D	huge_memory.c	35 #include <linux/oom.h>
/linux-master/kernel/cgroup/
H A D	cpuset.c	43 #include <linux/oom.h> 4839 * yes. If current has access to memory reserves as an oom victim, yes.
/linux-master/net/packet/
H A D	af_packet.c	1894 goto oom; 1924 oom:
/linux-master/kernel/trace/
H A D	ring_buffer.c	29 #include <linux/oom.h> 1509 * gracefully without invoking oom-killer and the system is not
/linux-master/kernel/
H A D	sysctl.c	58 #include <linux/oom.h>
H A D	fork.c	85 #include <linux/oom.h> 683 * Don't duplicate many vmas if we've been oom-killed (for
H A D	exit.c	59 #include <linux/oom.h>
H A D	cpu.c	18 #include <linux/oom.h>
/linux-master/fs/
H A D	exec.c	61 #include <linux/oom.h>
/linux-master/drivers/net/
H A D	virtio_net.c	2151 bool oom; local 2161 oom = err == -ENOMEM; 2173 return !oom; 2433 /* Make sure we have some buffers: if oom use wq. */
/linux-master/kernel/power/
H A D	process.c	10 #include <linux/oom.h> 146 * killable tasks. There is no guarantee oom victims will
/linux-master/drivers/gpu/drm/i915/
H A D	i915_driver.c	33 #include <linux/oom.h>
/linux-master/kernel/rcu/
H A D	tree.c	57 #include <linux/oom.h>

Completed in 838 milliseconds

123

Indexes created Mon May 20 13:24:45 MDT 2024