public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David L. Parsley" <parsley@linuxjedi.org>
To: linux-kernel@vger.kernel.org
Subject: /proc/sys/vm/freepages read-only?!?
Date: Mon, 26 Mar 2001 10:44:19 -0500	[thread overview]
Message-ID: <3ABF63D3.D0C8558@linuxjedi.org> (raw)

Hi,

I'm trying to do some vm tuning for diskless (and therefore swapless)
devices.  (I'm working on a distro that tftp's packages and runs
entirely in RAM)

Even on an X terminal with 64MB RAM, badly behaved apps can use lots of
ram in the Xserver, and what I'm seeing is a hang.  The box is usually
still pingable, just unresponsive.  I'm using cramfs pretty heavily, and
I think what's occuring is that the terminal gets too low on freepages,
and since pages used by X can't be swapped out, the box starts thrashing
the vm and is unable to get pages to uncompress into.

My first thought was echo (bigger numbers) > /proc/sys/vm/freepages -
but lo! - it's not writable anymore.  I found comments in page_alloc.c
indicating it had to be read-only, but it seems it's only a safety
precaution.  Something along the lines of values too small being 'bad
bad'.


help?
	David
-- 
David L. Parsley
Network Administrator
Roanoke College

                 reply	other threads:[~2001-03-26 15:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3ABF63D3.D0C8558@linuxjedi.org \
    --to=parsley@linuxjedi.org \
    --cc=linux-kernel@vger.kernel.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