From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: "David L. Parsley" <parsley@linuxjedi.org>
Cc: linux-mm@kvack.org
Subject: Re: memory mgmt/tuning for diskless machines
Date: Mon, 2 Apr 2001 22:04:24 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0104022159430.6947-100000@freak.distro.conectiva> (raw)
In-Reply-To: <3ABF501D.CB800A16@linuxjedi.org>
On Mon, 26 Mar 2001, David L. Parsley wrote:
> Hi,
>
> I'm working on a project for building diskless multimedia terminals/game
> consoles. One issue I'm having is my terminal seems to go OOM and crash
> from time to time. It's strange, I would expect the OOM killer to blow
> away X, but it doesn't - the machine just becomes unresponsive.
>
> Since this is a quasi-embedded platform, what I'd REALLY like to do is
> tune the vm so mallocs fail when freepages falls below a certain point.
> I'm using cramfs, and what I suspect is happening is that once memory
> gets too low, the kernel doesn't have enough memory to uncompress
> pages. Since there's no swap, there's nothing to page out.
>
> So... it occured to me I could tune this with /proc/sys/vm/freepages -
> but now I find that it's read-only, and I can't echo x y z > freepages
> like I used to. What's up with that?
It should work. Are you sure you're trying to change it as root ?
> Suggestions?
Which kernel version are you using ?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-04-03 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 14:20 David L. Parsley
2001-03-26 16:00 ` Rik van Riel
2001-03-26 16:30 ` David L. Parsley
2001-03-26 17:15 ` Jonathan Morton
2001-04-03 1:04 ` Marcelo Tosatti [this message]
2001-04-03 9:44 Szabolcs Szakacsits
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0104022159430.6947-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=parsley@linuxjedi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox