From: Nicholas Knight <nknight@pocketinet.com>
To: vda <vda@port.imtp.ilyichevsk.odessa.ua>, christian e <cej@ti.com>
Cc: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: minimizing swap usage
Date: Thu, 27 Dec 2001 19:52:48 -0800 [thread overview]
Message-ID: <WHITEidGVwPGxgelXDe00000748@white.pocketinet.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112200559350.8883-100000@shell1.aracnet.com> <3C2B0A5A.4070101@ti.com> <01122714150100.12566@manta>
In-Reply-To: <01122714150100.12566@manta>
On Thursday 27 December 2001 08:15 am, vda wrote:
> On Thursday 27 December 2001 09:47, christian e wrote:
> > > I've just installed 2.4.17 and so far it seems better.According
> > > to changelog there has been some changes to swap behaviour.Can I
> > > make it even more aggressive to cut down on buffers+cache somehow
> > > ??
> >
> > sorry ,my bad.After using it for some hours it's just as
> > bad.Rechecked the changelog and it was already done in the previous
> > kernel i used (17-rc1 ).Same problem with lots of cache and plenty
> > of swapping :-(
>
> Ok, let's try to collect some data.
> I ask (knowledgeable) list members to say whether they see something
> unusual
>
> You may find below
> 1) top of my box running normally
> 2) top after killall5 -15; killall5 -9
> 3) /proc/mounts
>
> Why proc/mounts? There you will see that my box is exclusively NFSed.
> AFAIK nfs mounts do not cache large amounts of data on the client
> size. Note that when you try to explain top (2).
You're not understanding. This is not a bug. This is intended behavior.
The problem is that this behavior is not neccisarily desirable. I have
attempted to propose something that can be TRIED in order to attempt to
optimize swap behavior for certain situations, primarily desktop usage.
This is not a bug.
There is nothing unusual about it.
I am not attempting to report a bug.
There is no need to collect data.
We have all the data we need from any number of complaints about
current swap behavior.
Something needs to be tried, I proposed something to be tried, I did
not report a bug, I did not say this was unusual for 2.4.x series.
prev parent reply other threads:[~2001-12-28 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 13:30 christian e
2001-12-20 14:05 ` M. Edward (Ed) Borasky
2001-12-25 11:02 ` Nicholas Knight
[not found] ` <01122513421800.02101@manta>
2001-12-25 11:50 ` Nicholas Knight
[not found] ` <3C2B0A5A.4070101@ti.com>
[not found] ` <01122714150100.12566@manta>
2001-12-28 3:52 ` Nicholas Knight [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=WHITEidGVwPGxgelXDe00000748@white.pocketinet.com \
--to=nknight@pocketinet.com \
--cc=cej@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=znmeb@aracnet.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®