From: Anders Karlsson <anders@trudheim.com>
To: Karl Vogel <karl.vogel@seagha.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: How do I make this thing stop laging? Reboot? Sounds like Windows!
Date: 18 Jun 2003 11:23:31 +0100 [thread overview]
Message-ID: <1055931810.2285.24.camel@tor.trudheim.com> (raw)
In-Reply-To: <E19SZ8v-0005Ie-00@relay-1.seagha.com>
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
On Wed, 2003-06-18 at 10:22, Karl Vogel wrote:
> On 18 Jun 2003, you wrote in linux.kernel:
>
> > rmoser wrote:
> > [...]
[...]
> > Because the problem _is_ unsolvable. You want the kernel
> > to go "oh, lots of free memory showed up, lets pull
> > everything in from swap just in case someone might need it."
>
>
> You might want to try Con Kolivas' patches on:
> http://members.optusnet.com.au/ckolivas/kernel/
>
> More specifically the 'swap prefetch' patch. From this FAQ:
>
> --
> Swap prefetching? If you have >10% free physical ram and any used swap it
> will start swapping pages back into physical ram. Probably not of real
> benefit but many people like this idea. I have a soft spot for it and like
> using it.
> --
>
> The disadvantage is ofcourse that you will be using up more RAM than is
> really necessary.
Sorry for breaking in, but this is an interesting discussion. :-)
I find that the Linux VM tend to push things out in to swap-space when
it does not need it. This is fine. However, I was once told something
about AIX that has lodged itself in the back of my mind.
AIX uses (or used to use) the exact same way of reading/writing data
from/to disk for all I/O. AIX also makes a distinction between code and
data. If code in RAM is unused, it simply gets flushed. If it is needed
again at a later time, it is paged in from disk where it was originally
loaded from. Only dirty data is paged out into swap.
Is it feasible to tweak the Linux VM to behave in the same fashion? If
Linux already does it this way, I'll just shut up. :)
/A
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2003-06-18 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 0:30 How do I make this thing stop laging? Reboot? Sounds like Windows! rmoser
2003-06-18 8:22 ` Helge Hafting
2003-06-18 9:22 ` Karl Vogel
2003-06-18 9:44 ` Oliver Neukum
2003-06-18 10:23 ` Anders Karlsson [this message]
2003-06-18 15:08 ` Gianni Tedesco
2003-06-18 16:43 ` Joe
2003-06-18 9:30 ` Yaroslav Rastrigin
2003-06-18 11:02 ` Helge Hafting
2003-06-18 12:17 ` Mike Galbraith
2003-06-19 8:04 ` H. Peter Anvin
2003-06-19 10:00 ` Helge Hafting
2003-06-19 10:02 ` Nick Piggin
2003-06-19 15:54 ` Daniel Gryniewicz
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 9:56 Karl Vogel
2003-06-18 16:53 ` Oliver Neukum
2003-06-18 10:43 Karl Vogel
2003-06-18 10:49 Karl Vogel
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=1055931810.2285.24.camel@tor.trudheim.com \
--to=anders@trudheim.com \
--cc=karl.vogel@seagha.com \
--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