From: Joe <joe@lexus.com>
To: linux-kernel@vger.kernel.org
Subject: Re: How do I make this thing stop laging? Reboot? Sounds like Windows!
Date: Wed, 18 Jun 2003 09:43:57 -0700 [thread overview]
Message-ID: <3EF096CD.8060407@lexus.com> (raw)
In-Reply-To: <E19SZ8v-0005Ie-00@relay-1.seagha.com>
Karl Vogel wrote:
>On 18 Jun 2003, you wrote in linux.kernel:
>
>
>
>>rmoser wrote:
>>[...]
>>
>>
>>>Ten minutes later I get the brains to run top. It seems I have about
>>>50 MB in swap, and 54 MB free memory. So I wait ten minutes more.
>>>
>>>No change.
>>>
>>>% swapoff -a; swapon -a
>>>
>>>Fixes all my problems.
>>>
>>>Now this long story shows something: The kernel appears to be unable
>>>to intelligently pull swap back into RAM. What gives?
>>>
>>>
>>>
>>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/
>
>
Unfortunately he provided no information as to
what kernel and/or distro he is running - for all
we know he's running 2.4.9 - so the con man's
patches probably won't apply.
Joe
>
>
next prev parent reply other threads:[~2003-06-18 16:30 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
2003-06-18 15:08 ` Gianni Tedesco
2003-06-18 16:43 ` Joe [this message]
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=3EF096CD.8060407@lexus.com \
--to=joe@lexus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.