From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.28 -> ch..ch...changes....
Date: Sat, 27 Nov 2004 15:42:27 +0000 [thread overview]
Message-ID: <200411271542.27896.nick@linicks.net> (raw)
In-Reply-To: <877jo8u8q1.fsf@amaterasu.srvr.nix>
On Friday 26 November 2004 11:53, Nix wrote:
> On 24 Nov 2004, Nick Warne mused:
> > Normally memory slowly fills up, perhaps using swap for a bit under these
> > circumstances - but looking afterwards:
>
> This is a feature, not a bug. Free memory is wasted memory (although
> some has to be kept free for drivers that need GFP_ATOMIC allocations:
> i.e. `memory *now* dammit *now*'.
>
> > root@linuxamd:~# free
> > total used free shared buffers cached
> > Mem: 1292348 520012 772336 0 38596 327304
> > -/+ buffers/cache: 154112 1138236
> > Swap: 1959888 0 1959888
>
> The only thing I can think of that causes this is something very
> memory-hungry that's just been killed, releasing a pile of pages back to
> the system.
>
> > But whatever, I am impressed indeed - somethings changed for the good!!!
>
> I see no signs of such a change on my 2.4.28 boxes:
~snip~
Ummm. I do, though. Maybe the cause is I am getting more experienced, and
building kernels now, I _do_ the right things. But for some reason I do find
2.4.28 a lot more responsive to memory usage - I really do.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
prev parent reply other threads:[~2004-11-27 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 21:36 2.4.28 -> ch..ch...changes Nick Warne
2004-11-24 7:08 ` Marcelo Tosatti
2004-11-24 17:48 ` Hugh Dickins
2004-11-24 19:57 ` Nick Warne
2004-11-26 11:53 ` Nix
2004-11-27 15:42 ` Nick Warne [this message]
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=200411271542.27896.nick@linicks.net \
--to=nick@linicks.net \
--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.