public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sebastian Dröge" <sebastian.droege@gmx.de>
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: [VM] 2.4.14/15-pre4 too "swap-happy"?
Date: Wed, 14 Nov 2001 13:44:43 +0100	[thread overview]
Message-ID: <20011114124337Z280554-17408+14330@vger.kernel.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
Are there any paramters (for example in /proc/sys/vm), which make the VM less 
swap-happy?
My problems are following:

I burn a CD-R on system 1:
...
- ---Swap: 0 KB
mkisofs blablabla
- ---swap begins to rise ;)
mkisofs finished
- ---swap: 3402 KB
cdrecord speed=12 blablabla (FIFO is 4 MB)
- ---heavy swapping
cdrecord finished
- ---swap: 27421 KB

The system has 256 MB RAM, nothing RAM-eating in the background I got many 
buffer-underuns just because of swapping. When I turn swap off everything 
works fine. I think it's something with the cache.

Leaving system 2 alone, just play mp3s over nfs:

After two or three days the used swap-space is around 3 MB. I just played 
MP3s and no X and no other "big" applications were running. This isn't really 
a problem but it doesn't look good. Just because of cache swap gets full :(

I think this must be fixed before opening 2.5.
It isn't good when something gets swapped out just because of the cache. 
It'll be better if the cache gets lesser priority.

system 1:
Kernel 2.4.15-pre4
Intel Pentium II @ 350 MHZ
256 MB RAM
512 MB Swap

system 2:
Kernel 2.4.14
AMD K6-2 @ 350 MHZ
128 MB RAM
256 MB Swap

If you need some more system information contact me and I'll post them
I'll be happy to test all your patches/suggestions :)

Thanks in advance
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE78mc+vIHrJes3kVIRAhooAJ4mp52iyrIkRPe/wicwrSxmIwmvYQCgg/NQ
MW522KOtGdhPdjRVbXwLrko=
=TlFS
-----END PGP SIGNATURE-----

             reply	other threads:[~2001-11-14 12:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 12:44 Sebastian Dröge [this message]
2001-11-14 15:00 ` [VM] 2.4.14/15-pre4 too "swap-happy"? Rik van Riel
     [not found] <200111141243.fAEChS915731@neosilicon.transmeta.com>
2001-11-14 16:34 ` Linus Torvalds
2001-11-19 18:01   ` Sebastian Dröge
2001-11-19 18:18   ` Simon Kirby
  -- strict thread matches above, loose matches on Subject: below --
2001-11-15  8:38 janne
2001-11-15  9:05 ` janne
2001-11-15 17:44   ` Mike Galbraith
2001-11-16  0:14     ` janne
     [not found] <200111191801.fAJI1l922388@neosilicon.transmeta.com>
2001-11-19 18:07 ` Linus Torvalds
2001-11-19 18:31   ` Ken Brownfield
2001-11-19 19:23     ` Linus Torvalds
2001-11-19 23:39       ` Ken Brownfield
2001-11-19 23:52         ` Linus Torvalds
2001-11-20  0:18           ` M. Edward (Ed) Borasky
2001-11-20  0:25           ` Ken Brownfield
2001-11-20  0:31             ` Linus Torvalds
2001-11-20  3:09           ` Ken Brownfield
2001-11-20  3:30             ` Linus Torvalds
2001-11-20  3:32             ` Andrea Arcangeli
2001-11-20  5:54               ` Ken Brownfield
2001-11-20  6:50                 ` Linus Torvalds
2001-11-19 19:30     ` Ken Brownfield
2001-11-19 18:26       ` Marcelo Tosatti
2001-11-19 19:44   ` Slo Mo Snail
2001-11-20  0:48 Yan, Noah

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=20011114124337Z280554-17408+14330@vger.kernel.org \
    --to=sebastian.droege@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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