Dave Peterson wrote:
The patch below modifies the behavior of the OOM killer so that only
one OOM kill operation can be in progress at a time. When running a
test program that eats lots of memory, I was observing behavior where
the OOM killer gets impatient and shoots one or more system daemons
in addition to the program that is eating lots of memory. This fixes
the problematic behavior.
Hi Dave,
Firstly why not use a semaphore and trylocks instead of your homebrew
lock?
Second, can you arrange it without using the extra field in mm_struct
and operation in the mmput fast path?
--
Send instant messages to your online friends http://au.messenger.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
