From: Bob McElrath <mcelrath@draal.physics.wisc.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stephan von Krawczynski <skraw@ithnet.com>, linux-kernel@vger.kernel.org
Subject: Re: "Cached" grows and grows and grows...
Date: Fri, 7 Sep 2001 17:24:33 -0500 [thread overview]
Message-ID: <20010907172433.E5598@draal.physics.wisc.edu> (raw)
In-Reply-To: <20010907191349.457cad95.skraw@ithnet.com> <E15fTuS-0002g1-00@the-village.bc.nu>
In-Reply-To: <E15fTuS-0002g1-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Sep 07, 2001 at 11:15:36PM +0100
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Alan Cox [alan@lxorguk.ukuu.org.uk] wrote:
> > To tell you the honest truth: you are not alone in cosmos (with this problem)
> > ;-)
> > To give you that explicit hint for saving money: do not buy mem, it will be
> > eaten up by recent kernels without any performance gain or other positive
> > impact whatsoever.
>
> Pick up a 2.4.9-ac kernel, and you shouldnt be seeing the problem (I say
> shouldnt, I'm not 100% convinced its all under control)
Hmmm...that will make my kernel 2.4.10pre4aa1acX-xfs. Ack! ;)
Maybe I can wait 'til 2.4.10. Then it will only be 2.4.10aa1acX-xfs.
;)
Cheers,
-- Bob
Bob McElrath (rsmcelrath@students.wisc.edu)
Univ. of Wisconsin at Madison, Department of Physics
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-09-07 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 16:08 Bob McElrath
2001-09-07 17:13 ` Stephan von Krawczynski
2001-09-07 22:15 ` Alan Cox
2001-09-07 22:24 ` Bob McElrath [this message]
2001-09-08 0:53 ` VM improvement in -ac [was: "Cached" grows and grows and grows...] Mike Fedyk
2001-09-08 16:47 ` "Cached" grows and grows and grows Stephan von Krawczynski
2001-09-08 17:14 ` Alan Cox
2001-09-09 13:15 ` Stephan von Krawczynski
2001-09-09 13:34 ` Alan Cox
2001-09-26 1:55 M. Edward Borasky
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=20010907172433.E5598@draal.physics.wisc.edu \
--to=mcelrath@draal.physics.wisc.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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
all inboxes | Powered by JetHome®