Home
last modified time | relevance | path

Searched refs:killed (Results 1 – 26 of 26) sorted by relevance

/linux-4.1.27/Documentation/
DSAK.txt47 actually want killed. This is because these applications are
51 You can identify processes which will be killed by SAK with the
62 So `gpm' will be killed by SAK. This is a bug in gpm. It should
Datomic_ops.txt472 obj->killed = 1;
478 "obj->killed = 1;" is visible.
/linux-4.1.27/mm/
Doom_kill.c716 int killed = 0; in __out_of_memory() local
765 killed = 1; in __out_of_memory()
772 if (killed) in __out_of_memory()
/linux-4.1.27/drivers/staging/android/
DKconfig29 Registers processes to be killed when memory is low
/linux-4.1.27/drivers/block/paride/
DTransition-notes106 Corollary 1: ps_tq_active can be killed. Indeed, the only place where we
112 Corollary 2: ps_spinlock can be killed. Indeed, Lemma 1 and Lemma 2 show
118 can be killed. Indeed, we are not holding pd_lock and thus pd_busy is already
/linux-4.1.27/Documentation/vm/
Dovercommit-accounting19 this means a process will not be killed while accessing
Dhwpoison.txt17 * running process can just be killed directly instead. This implies
/linux-4.1.27/Documentation/cgroups/
Dmemcg_test.txt229 will be killed by the kernel.
231 in other groups shouldn't be killed.
/linux-4.1.27/kernel/
Dfork.c819 int killed; in wait_for_vfork_done() local
822 killed = wait_for_completion_killable(vfork); in wait_for_vfork_done()
825 if (killed) { in wait_for_vfork_done()
832 return killed; in wait_for_vfork_done()
/linux-4.1.27/arch/blackfin/
DKconfig.debug45 signal to be killed. If you are getting HW errors in your system,
97 Misbehaving applications will be killed (generate a SEGV) while the
/linux-4.1.27/drivers/net/wireless/orinoco/
Dorinoco_usb.c273 int killed; member
332 ctx->killed = 1; in ezusb_request_timerfn()
533 if (ctx->killed) { in ezusb_request_out_callback()
/linux-4.1.27/fs/
Dexec.c919 goto killed; in de_thread()
947 goto killed; in de_thread()
1043 killed: in de_thread()
/linux-4.1.27/Documentation/usb/
Dcallbacks.txt86 killed by usbcore. Note that in this case disconnect will be called some
Dusbmon.txt75 This process will read until it is killed. Naturally, the output can be
/linux-4.1.27/Documentation/blockdev/
DREADME.DAC960373 have been killed simultaneously, this command may be used to bring all but
458 DAC960#0: Physical Drive 1:1 killed because of timeout on SCSI command
492 functioning drive, or if the physical drive was killed without having failed
629 DAC960#0: Physical Drive 1:2 killed because of timeout on SCSI command
631 DAC960#0: Physical Drive 1:2 killed because it was removed
/linux-4.1.27/Documentation/serial/
Dtty.txt8 them so they can eventually be killed off.
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dentry.S408 ;; do the RBFexit since we might have killed off the running
/linux-4.1.27/Documentation/target/
Dtcmu-design.txt234 Userspace handler process is killed:
/linux-4.1.27/Documentation/sysctl/
Dvm.txt597 memory when killed.
687 may be killed by oom-killer. No panic occurs in this case.
/linux-4.1.27/Documentation/filesystems/
Dproc.txt1426 process gets killed in out of memory conditions.
1475 avoids servers and important system daemons from being killed and loses the
1484 process should be killed in an out-of-memory situation.
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES401 cifs stats. Fix oops in unmount when cifsd thread being killed by
576 to kernel log when application with open network files killed.
/linux-4.1.27/drivers/watchdog/
DKconfig45 get killed. If you say Y here, the watchdog cannot be stopped once
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq1446 * instead of being killed by SCSIEN getting cleared.
/linux-4.1.27/Documentation/trace/
Dftrace.txt167 if it were to be killed by a signal, this file can be used
/linux-4.1.27/Documentation/scsi/
DChangeLog.lpfc1387 modprobe are killed via ctrl-c
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt986 be categorized. You will find messages such as "You killed Speakup",