[lkml]   [2004]   [Aug]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
SubjectRe: oom-killer
On Wed, Aug 18, 2004 at 02:55:42PM +0200, Anders Saaby wrote:
> This is a high-volume NFS server running almost no user-space
> applications. It serves a handfull of web server NFS clients from a
> ~700G XFS filesystem. The machine has about 2.5 GB of RAM and 4G of
> swap (which is almost not in use - i may use 5-10 MB total tops).
> CONFIG_HIGHMEM and CONFIG_HIGHMEM4G enabled, SMP enabled, preempt disabled.
> Today the OOM killer kicked in - it seemed that swap was almost unused at the
> time (which is strange, as that should prevent the OOM killer from kicking
> in).
> Relevant part of the syslog follows (syslogd was killed too eventually):

This seems to have been meant to resolve laptop_mode issues, but looks
like it didn't get applied. I'm not convinced it will help given that
you appear to have a vanilla ZONE_NORMAL slab OOM (858MB slab), but you
never know. Capturing /proc/slabinfo data may be more helpful.

Index: oom-2.6.8-rc1/mm/vmscan.c
--- oom-2.6.8-rc1.orig/mm/vmscan.c 2004-07-14 06:17:13.876343912 -0700
+++ oom-2.6.8-rc1/mm/vmscan.c 2004-07-14 06:22:15.986416200 -0700
@@ -417,7 +417,8 @@
goto keep_locked;
if (!may_enter_fs)
goto keep_locked;
- if (laptop_mode && !sc->may_writepage)
+ if (laptop_mode && !sc->may_writepage &&
+ !PageSwapCache(page))
goto keep_locked;

/* Page is dirty, try to write it out here */
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at
 \ /
  Last update: 2005-03-22 14:05    [W:0.043 / U:6.932 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site