lkml.org 
[lkml]   [1997]   [Dec]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Recipe for cooking 2.1.72's mm
On Tue, 16 Dec 1997, Pavel Machek wrote:

> Sorry. There is a problem. It needs to be solved, not worked
> around. (Notice, that same process does nothing bad to 2.0.28).

On my system, it just gives one or two out-of-memory kills
of random processes. I'd really like it if those processes
would be a little less random... Killing kerneld or crond
(or X... remember those poor stateless-vga-card users) is
IMHO worse than killing a program from some USER. Finding
the most hoggy non-root process group and killing some of
it's programs shouldn't be too difficult.

btw: I'm using 2.1.66 with my mmap-age patch...

> And: Work around is bad. Imagine your machine with such behaviour on
> 100MBit ethernet. Imagine me around (ping -f)ing your machine. That
> can keep your pages low for as long as I want. You do not your machine
> to go yo-yo (up and down and up and down ...).

Ok, so we should limit the amount of memory the kernel can grab
for internal usage... Sysctl-wise of course, because some people
have special purpose routing machines.

Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+



\
 
 \ /
  Last update: 2005-03-22 13:40    [W:2.107 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site