login
Header Space

 
 

Re: OOM killer problem - how to read the kernel log?

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Tobias Brox <tobixen@...>
Cc: <linux-kernel@...>
Date: Friday, November 9, 2007 - 5:54 pm

"Tobias Brox" <tobixen@gmail.com> writes:


Big-time.  There are a lot of "artificial" internal kernel memory
limits in the 32-bit architecture, so you can run up against those
(triggering the OOM killer) even if you have plenty of application
memory.

32GB in the box actually might be counter-productive unless you're
running 64-bit, because just tracking that much memory will consume
precious low kernel RAM.

-Doug
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
OOM killer problem - how to read the kernel log?, Tobias Brox, (Fri Nov 9, 5:35 pm)
Re: OOM killer problem - how to read the kernel log?, Johannes Weiner, (Sat Nov 10, 10:02 am)
Re: OOM killer problem - how to read the kernel log?, Tobias Brox, (Sat Nov 10, 12:09 pm)
Re: OOM killer problem - how to read the kernel log?, Douglas McNaught, (Fri Nov 9, 5:54 pm)
speck-geostationary