It doesn't dealloc memory. Ever. Which makes leaving it up for more than a
few hours fatal. I only have 64M (somebody wanna send me a 64M SDRAM
DIMM?:) in this box, and 32M swap (I don't wanna repartition;). What's it
doing? I'm not entirely sure. Looks to me like it's sizing up everything
you run, then adding IT'S memory into it's own.
Now, is there a FEASABLE way that we could do forced deallocation by PID
and/or memaddr in the kernel? By feasable, I mean it doesn't trash
everything when it does it, and only forces the dealloc if the matching
PID is dead. Because the way I *PREFER* to run X, I'll need to upgrade
this box to the full 1G to keep X going. ;P
-Phil R. Jaenke (kernel@nls.net / prj@nls.net)
TheGuyInCharge(tm), Ketyra Designs - We get paid to break stuff :)
Linux pkrea.ketyra.INT 2.0.33 #15 Sat Apr 18 00:40:21 EDT 1998 i586
Linux eiterra.nls.net 2.1.98 #15 Fri May 1 18:21:00 EDT 1998 i586
- Linus says for 'brave people only.' I say 'keep a backup.' - :)
! I reserve the right to bill spammers for my time and disk space !
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu