Home
last modified time | relevance | path

Searched refs:oom (Results 1 – 25 of 28) sorted by relevance

12

/linux-5.19.10/arch/x86/um/vdso/
Dvma.c31 goto oom; in init_vdso()
37 goto oom; in init_vdso()
45 oom: in init_vdso()
/linux-5.19.10/arch/sparc/vdso/
Dvma.c266 goto oom; in init_vdso_image()
272 goto oom; in init_vdso_image()
277 goto oom; in init_vdso_image()
289 goto oom; in init_vdso_image()
294 goto oom; in init_vdso_image()
298 goto oom; in init_vdso_image()
308 oom: in init_vdso_image()
/linux-5.19.10/fs/nfsd/
Dauth.c47 goto oom; in nfsd_setuser()
56 goto oom; in nfsd_setuser()
90 oom: in nfsd_setuser()
/linux-5.19.10/security/selinux/
Dnetlink.c78 goto oom; in selnl_notify()
93 oom: in selnl_notify()
/linux-5.19.10/include/net/
Dfq_impl.h203 bool oom; in fq_tin_enqueue() local
230 oom = (fq->memory_usage > fq->memory_limit); in fq_tin_enqueue()
231 while (fq->backlog > fq->limit || oom) { in fq_tin_enqueue()
241 if (oom) { in fq_tin_enqueue()
243 oom = (fq->memory_usage > fq->memory_limit); in fq_tin_enqueue()
/linux-5.19.10/tools/testing/fault-injection/
Dfailcmd.sh34 --oom-kill-allocating-task=value
89 LONGOPTS=$LONGOPTS,reject-start:,reject-end:,oom-kill-allocating-task:,help
178 --oom-kill-allocating-task)
/linux-5.19.10/drivers/media/pci/solo6x10/
Dsolo6x10-g723.c125 goto oom; in snd_solo_pcm_open()
132 goto oom; in snd_solo_pcm_open()
142 oom: in snd_solo_pcm_open()
/linux-5.19.10/Documentation/translations/zh_CN/admin-guide/
Dsysrq.rst44 64 = 0x40 - 使能对进程的信号操作 (term, kill, oom-kill)
106 ``f`` 将调用 oom killer 杀掉一个过度占用内存的进程,如果什么任务都没杀,
/linux-5.19.10/mm/
Dpage_ext.c413 goto oom; in page_ext_init()
422 oom: in page_ext_init()
Dmemory.c3096 goto oom; in wp_page_copy()
3102 goto oom; in wp_page_copy()
3107 goto oom; in wp_page_copy()
3232 oom: in wp_page_copy()
4075 goto oom; in do_anonymous_page()
4078 goto oom; in do_anonymous_page()
4130 oom: in do_anonymous_page()
/linux-5.19.10/Documentation/vm/
Dindex.rst28 oom
/linux-5.19.10/drivers/net/ethernet/dec/tulip/
Dinterrupt.c322 goto oom; in tulip_poll()
348 goto oom; in tulip_poll()
352 oom: /* Executed with RX ints disabled */ in tulip_poll()
/linux-5.19.10/include/trace/events/
Doom.h3 #define TRACE_SYSTEM oom
/linux-5.19.10/drivers/net/ethernet/marvell/
Dmv643xx_eth.c381 u8 oom; member
612 mp->oom = 1; in rxq_refill()
613 goto oom; in rxq_refill()
649 oom: in rxq_refill()
2251 if (unlikely(mp->oom)) { in mv643xx_eth_poll()
2252 mp->oom = 0; in mv643xx_eth_poll()
2270 if (likely(!mp->oom)) in mv643xx_eth_poll()
2293 } else if (!mp->oom && (mp->work_rx_refill & queue_mask)) { in mv643xx_eth_poll()
2301 if (mp->oom) in mv643xx_eth_poll()
2456 if (mp->oom) { in mv643xx_eth_open()
/linux-5.19.10/tools/testing/selftests/cgroup/
Dtest_memcontrol.c395 long low, oom; in test_memcg_protection() local
397 oom = cg_read_key_long(children[i], "memory.events", "oom "); in test_memcg_protection()
400 if (oom) in test_memcg_protection()
/linux-5.19.10/drivers/net/ethernet/natsemi/
Dnatsemi.c562 int oom; member
1840 if (np->oom) { in netdev_timer()
1842 np->oom = 0; in netdev_timer()
1845 if (!np->oom) { in netdev_timer()
1954 np->oom = 1; in refill_rx()
1986 np->oom = 0; in init_ring()
2388 if (np->oom) in netdev_rx()
/linux-5.19.10/drivers/net/ethernet/ibm/emac/
Dcore.c1074 goto oom; in emac_resize_rx_ring()
1105 oom: in emac_resize_rx_ring()
1247 goto oom; in emac_open()
1293 oom: in emac_open()
1793 goto oom; in emac_poll_rx()
1801 goto oom; in emac_poll_rx()
1845 oom: in emac_poll_rx()
/linux-5.19.10/Documentation/admin-guide/cgroup-v1/
Dmemory.rst54 - oom-killer disable knob and oom-notifier
89 memory.oom_control set/show oom controls.
284 When oom event notifier is registered, event will be delivered.
846 (if 1, oom-killer is disabled)
940 (Expect a bunch of notifications, and eventually, the oom-killer will
/linux-5.19.10/Documentation/admin-guide/
Dsysrq.rst32 64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
100 ``f`` Will call the oom killer to kill a memory hog process, but do not
/linux-5.19.10/Documentation/x86/
Dearlyprintk.rst141 …SysRq : HELP : loglevel(0-9) reBoot Crashdump terminate-all-tasks(E) memory-full-oom-kill(F) kill-…
/linux-5.19.10/Documentation/filesystems/
Dproc.rst37 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
39 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1610 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1614 process gets killed in out of memory (oom) conditions.
1623 The amount of "allowed" memory depends on the context in which the oom killer
1635 polarize the preference for oom killing either by always preferring a certain
1637 equivalent to disabling oom killing entirely for that task since it will always
1651 (OOM_DISABLE) to disable oom killing entirely for that task. Its value is
1659 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1662 This file can be used to check the current score used by the oom-killer for
/linux-5.19.10/Documentation/filesystems/caching/
Dfscache.rst182 | |oom=N |Number of acq reqs failed on ENOMEM |
/linux-5.19.10/drivers/net/ethernet/atheros/
Dag71xx.c1712 goto oom; in ag71xx_poll()
1746 oom: in ag71xx_poll()
/linux-5.19.10/Documentation/admin-guide/sysctl/
Dvm.rst817 may be killed by oom-killer. No panic occurs in this case.
822 above-mentioned. Even oom happens under memory cgroup, the whole
831 why oom happens. You can get snapshot.
/linux-5.19.10/drivers/net/
Dvirtio_net.c1435 bool oom; in try_fill_recv() local
1445 oom = err == -ENOMEM; in try_fill_recv()
1457 return !oom; in try_fill_recv()

12