From: Roger Larsson <roger.larsson@norran.net>
To: Anton Blanchard <anton@linuxcare.com.au>,
Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Benchmarking 2.2 and 2.4 using hdparm and dbench 1.1
Date: Tue, 9 Jan 2001 22:36:21 +0100 [thread overview]
Message-ID: <01010922362101.01377@dox> (raw)
In-Reply-To: <20010105004644.K13759@linuxcare.com> <Pine.LNX.4.21.0101041940490.5827-100000@svea.tellus> <20010109220810.K662@linuxcare.com>
In-Reply-To: <20010109220810.K662@linuxcare.com>
On Tuesday 09 January 2001 12:08, Anton Blanchard wrote:
> > Where is the size defined, and is it easy to modify?
>
> Look in fs/buffer.c:buffer_init()
>
> > I noticed that /proc/sys/vm/freepages is not writable any more. Is there
> > any reason for this?
>
> I am not sure why.
>
It can probably be made writeable, within limits (caused by zones...)
But the interesting part is that 2.4 tries to estimate how much memory it
will need shortly (inactive_target) and try to keep that amount inactive
clean (inactive_clean) - clean inactive memory can be freed and reused very
quickly.
cat /proc/meminfo
My feeling is that, for now, keeping it untuneable can help us in finding
fixable cases...
/RogerL
--
Home page:
http://www.norran.net/nra02596/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 17:43 Benchmarking 2.2 and 2.4 using hdparm and dbench 1.1 Tobias Ringstrom
2001-01-03 18:09 ` Daniel Phillips
2001-01-03 19:38 ` Tobias Ringstrom
2001-01-04 13:46 ` Anton Blanchard
2001-01-04 18:55 ` Tobias Ringstrom
2001-01-09 11:08 ` Anton Blanchard
2001-01-09 21:36 ` Roger Larsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 15:26 Tobias Ringstrom
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=01010922362101.01377@dox \
--to=roger.larsson@norran.net \
--cc=anton@linuxcare.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
/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.