mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Juha Saarinen" <juha@saarinen.org>
To: "Rik van Riel" <riel@conectiva.com.br>,
	"Josh Grebe" <squash@primary.net>
Cc: "Jan Harkes" <jaharkes@cs.cmu.edu>, <linux-kernel@vger.kernel.org>
Subject: RE: Question about memory usage in 2.4 vs 2.2
Date: Wed, 21 Mar 2001 10:29:31 +1200	[thread overview]
Message-ID: <LNBBIBDBFFCDPLBLLLHFEEAIJIAA.juha@saarinen.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0103201857170.3750-100000@imladris.rielhome.conectiva>

:: > And can this behavior be tuned so that it uses less of the overall
:: > memory?
::
:: This isn't currently possible. Also, I suspect what we really want
:: for most situations is a way to better balance between the different
:: uses of memory.  Again, patches are welcome (I haven't figured out a
:: way to take care of this balancing yet ... maybe we DO want some way
:: of limiting memory usage of each subsystem??).

man ulimit? ;-)

On a more serious note, is there a way to find out what has been paged out
to disk, and also limit what can be paged out?

I could be wrong, but for instance I leave X running for a while (not sure
about the timing here but let's say several hours), and come back and log in
again, it is very slow to "come alive". The screen redraws slowly, and
there's quite a bit of disk access. This only happens if the system is left
alone for a long period of time (no, I don't have APM running on it).

Squid behaves the same -- the first access after a long period of inactivity
causes a lot of disk grinding, but successive accesses are fine.

Don't see this behaviour with the 2.2.x kernels.


-- Juha


  reply	other threads:[~2001-03-20 22:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19  2:07 /proc/cpuinfo for Intel P4 D850GB asenec
2001-03-19  2:33 ` davej
2001-03-19  3:14 ` 2.4.3-pre4: Unable to handle kernel NULL pointer dereference at virtual address 000000fb Shawn Starr
2001-03-19 12:02 ` /proc/cpuinfo for Intel P4 D850GB David Weinehall
2001-03-19 21:58 ` 2.4.3-pre4: Unable to handle kernel NULL pointer dereference at virtual address 000000fb Shawn Starr
2001-03-20 17:01 ` Question about memory usage in 2.4 vs 2.2 Josh Grebe
2001-03-20 17:32   ` Jakob Østergaard
2001-03-20 20:29     ` Josh Grebe
2001-03-21 19:16       ` Jan Harkes
2001-03-21 19:54         ` Rik van Riel
2001-03-20 18:54   ` Jan Harkes
2001-03-20 20:29     ` Josh Grebe
2001-03-20 22:18       ` Rik van Riel
2001-03-20 22:29         ` Juha Saarinen [this message]
2001-03-21  9:28         ` Zou Min
2001-03-21  9:51           ` Andreas Dilger
2001-03-21 10:56             ` Zou Min
2001-03-21 10:14 Manfred Spraul
2001-03-21 17:42 ` Josh Grebe

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=LNBBIBDBFFCDPLBLLLHFEEAIJIAA.juha@saarinen.org \
    --to=juha@saarinen.org \
    --cc=jaharkes@cs.cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=squash@primary.net \
    /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

all inboxes | Powered by JetHome®