Home
last modified time | relevance | path

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

12

/openbmc/linux/arch/x86/um/vdso/
H A Dvma.c31 goto oom; in init_vdso()
37 goto oom; in init_vdso()
45 oom: in init_vdso()
/openbmc/linux/arch/sparc/vdso/
H A 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()
/openbmc/linux/fs/nfsd/
H A Dauth.c45 goto oom; in nfsd_setuser()
54 goto oom; in nfsd_setuser()
86 oom: in nfsd_setuser()
/openbmc/linux/include/net/
H A Dfq_impl.h204 bool oom; in fq_tin_enqueue() local
234 oom = (fq->memory_usage > fq->memory_limit); in fq_tin_enqueue()
235 while (fq->backlog > fq->limit || oom) { in fq_tin_enqueue()
245 if (oom) { in fq_tin_enqueue()
247 oom = (fq->memory_usage > fq->memory_limit); in fq_tin_enqueue()
/openbmc/linux/tools/testing/fault-injection/
H A Dfailcmd.sh34 --oom-kill-allocating-task=value
89 LONGOPTS=$LONGOPTS,reject-start:,reject-end:,oom-kill-allocating-task:,help
178 --oom-kill-allocating-task)
/openbmc/linux/security/selinux/
H A Dnetlink.c78 goto oom; in selnl_notify()
93 oom: in selnl_notify()
/openbmc/linux/drivers/media/pci/solo6x10/
H A 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()
/openbmc/linux/Documentation/translations/zh_CN/admin-guide/
H A Dsysrq.rst44 64 = 0x40 - 使能对进程的信号操作 (term, kill, oom-kill)
106 ``f`` 将调用 oom killer 杀掉一个过度占用内存的进程，如果什么任务都没杀，
/openbmc/linux/mm/
H A Dpage_ext.c474 goto oom; in page_ext_init()
483 oom: in page_ext_init()
H A Dmemory.c3087 goto oom; in wp_page_copy()
3092 goto oom; in wp_page_copy()
3097 goto oom; in wp_page_copy()
3222 oom: in wp_page_copy()
4149 goto oom; in do_anonymous_page()
4152 goto oom; in do_anonymous_page()
4209 oom: in do_anonymous_page()
/openbmc/linux/Documentation/mm/
H A Dindex.rst28 oom
/openbmc/linux/drivers/net/ethernet/dec/tulip/
H A Dinterrupt.c322 goto oom; in tulip_poll()
348 goto oom; in tulip_poll()
352 oom: /* Executed with RX ints disabled */ in tulip_poll()
/openbmc/linux/drivers/net/ethernet/marvell/
H A Dmv643xx_eth.c382 u8 oom; member
613 mp->oom = 1; in rxq_refill()
614 goto oom; in rxq_refill()
650 oom: in rxq_refill()
2252 if (unlikely(mp->oom)) { in mv643xx_eth_poll()
2253 mp->oom = 0; in mv643xx_eth_poll()
2271 if (likely(!mp->oom)) in mv643xx_eth_poll()
2294 } else if (!mp->oom && (mp->work_rx_refill & queue_mask)) { in mv643xx_eth_poll()
2302 if (mp->oom) in mv643xx_eth_poll()
2457 if (mp->oom) { in mv643xx_eth_open()
/openbmc/linux/include/trace/events/
H A Doom.h3 #define TRACE_SYSTEM oom
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dmemory.rst54 - oom-killer disable knob and oom-notifier
92 memory.oom_control set/show oom controls.
282 cgroup. (See :ref:`10. OOM Control <cgroup-v1-memory-oom-control>` below.)
295 When oom event notifier is registered, event will be delivered.
296 (See :ref:`oom_control <cgroup-v1-memory-oom-control>` section)
485 <cgroup-v1-memory-oom-control>` (below) and seeing what happens will be
834 .. _cgroup-v1-memory-oom-control:
877 (if 1, oom-killer is disabled)
971 (Expect a bunch of notifications, and eventually, the oom-killer will
/openbmc/linux/tools/testing/selftests/cgroup/
H A Dtest_memcontrol.c418 long low, oom; in test_memcg_protection() local
420 oom = cg_read_key_long(children[i], "memory.events", "oom "); in test_memcg_protection()
423 if (oom) in test_memcg_protection()
/openbmc/linux/drivers/net/ethernet/natsemi/
H A 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()
/openbmc/linux/drivers/net/ethernet/ibm/emac/
H A Dcore.c1075 goto oom; in emac_resize_rx_ring()
1106 oom: in emac_resize_rx_ring()
1248 goto oom; in emac_open()
1294 oom: in emac_open()
1794 goto oom; in emac_poll_rx()
1802 goto oom; in emac_poll_rx()
1846 oom: in emac_poll_rx()
/openbmc/linux/Documentation/admin-guide/
H A 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
/openbmc/linux/Documentation/arch/x86/
H A Dearlyprintk.rst141 …SysRq : HELP : loglevel(0-9) reBoot Crashdump terminate-all-tasks(E) memory-full-oom-kill(F) kill-…
/openbmc/linux/Documentation/filesystems/
H A 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
1641 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1645 process gets killed in out of memory (oom) conditions.
1654 The amount of "allowed" memory depends on the context in which the oom killer
1666 polarize the preference for oom killing either by always preferring a certain
1668 equivalent to disabling oom killing entirely for that task since it will always
1682 (OOM_DISABLE) to disable oom killing entirely for that task. Its value is
1690 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1693 This file can be used to check the current score used by the oom-killer for
/openbmc/linux/Documentation/filesystems/caching/
H A Dfscache.rst182 | |oom=N |Number of acq reqs failed on ENOMEM |
/openbmc/linux/drivers/net/ethernet/atheros/
H A Dag71xx.c1713 goto oom; in ag71xx_poll()
1747 oom: in ag71xx_poll()
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dvm.rst815 may be killed by oom-killer. No panic occurs in this case.
820 above-mentioned. Even oom happens under memory cgroup, the whole
829 why oom happens. You can get snapshot.
/openbmc/linux/drivers/net/
H A Dvirtio_net.c2013 bool oom; in try_fill_recv() local
2023 oom = err == -ENOMEM; in try_fill_recv()
2035 return !oom; in try_fill_recv()

12