From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Takao Indoh <indou.takao@soft.fujitsu.com>
Subject: Re: cache limit
Date: Tue, 26 Aug 2003 12:15:46 +0200 [thread overview]
Message-ID: <3F4B3352.4000703@softhome.net> (raw)
In-Reply-To: <oyDw.5FP.33@gated-at.bofh.it>
Mike Fedyk wrote:
>>On Mon, Aug 25, 2003 at 11:45:58AM +0900, Takao Indoh wrote:
>>
>>>I need a tuning parameter which can control pagecache
>>>like /proc/sys/vm/pagecache, which RedHat Linux has.
>>>The latest 2.4 or 2.5 standard kernel does not have such a parameter.
>>>2.4.18 kernel or 2.4-aa kernel has a alternative method?
>
> I doubt that there will be that option in the 2.4 stable series. I think
> you are trying to fix the problem without understanding the entire picture.
> If there is too much pagechache, then the kernel developers need to know
> about your workload so that they can fix it. But you have to try -aa first
> to see if it's already fixed.
>
Let me give my point of view.
Linux trys to scale up to the limits of given hardware.
That is _*horribly*_ wrong.
If I have 1GB of memory and my applications for use only 16MB - it
doesn't mean I want to fill 1GB-16MB with garbage like file my momy had
viewed two weeks ago.
That's it: OS should scale for *application* *needs*.
Can you compare in your mind overhead of managing 1GB of cache with
managing e.g. 16MB of cache?
So IMHO problem is: OS needless overhead.
It is possible to minimize overhead in several ways:
1) Optimize algorithms and data structures.
2) Minimize amount of resources.
3) As a compromise of 1&2 - teach OS to not use unneeded resource til
the time they will be really needed, and free them afterwards.
1) is already done, 3) is awful heuristics which will never work
reliably.
And Takao's patch was trying to approach problem from 2) point.
So as for me it is justified.
Comments are welcome.
next parent reply other threads:[~2003-08-26 10:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <n7lV.2HA.19@gated-at.bofh.it>
[not found] ` <ofAJ.4dx.9@gated-at.bofh.it>
[not found] ` <ogZM.5KJ.1@gated-at.bofh.it>
[not found] ` <oyDw.5FP.33@gated-at.bofh.it>
2003-08-26 10:15 ` Ihar 'Philips' Filipau [this message]
2003-08-26 17:46 ` cache limit Mike Fedyk
2003-08-27 16:03 Joseph Malicki
[not found] <000801c36cb1$454d4950$1001a8c0@etofmv650>
2003-08-27 16:02 ` YoshiyaETO
[not found] <oJ5P.699.21@gated-at.bofh.it>
[not found] ` <oJ5P.699.23@gated-at.bofh.it>
[not found] ` <oJ5P.699.25@gated-at.bofh.it>
[not found] ` <oJ5P.699.27@gated-at.bofh.it>
[not found] ` <oJ5P.699.19@gated-at.bofh.it>
[not found] ` <oQh2.4bQ.13@gated-at.bofh.it>
2003-08-26 19:08 ` Ihar 'Philips' Filipau
2003-08-26 19:23 ` Mike Fedyk
2003-08-27 10:21 ` Ihar 'Philips' Filipau
2003-08-27 11:07 ` Nick Piggin
[not found] <m6Bv.3ys.1@gated-at.bofh.it>
[not found] ` <mLY8.dO.5@gated-at.bofh.it>
2003-08-21 9:52 ` Ihar 'Philips' Filipau
2003-08-25 7:17 ` Takao Indoh
-- strict thread matches above, loose matches on Subject: below --
2003-08-19 4:39 Anthony R.
2003-08-19 4:57 ` Nuno Silva
2003-08-19 5:33 ` Denis Vlasenko
2003-08-19 6:20 ` Andrew Morton
2003-08-19 9:05 ` J.A. Magallon
2003-08-19 9:16 ` Andrew Morton
2003-08-19 9:28 ` J.A. Magallon
2003-08-19 9:43 ` Andrew Morton
2003-08-19 13:32 ` Erik Andersen
2003-08-19 20:56 ` Andrew Morton
2003-08-19 14:28 ` Anthony R.
2003-08-19 18:26 ` Mike Fedyk
2003-08-19 5:42 ` Nick Piggin
2003-08-21 0:49 ` Takao Indoh
2003-08-21 23:47 ` Mike Fedyk
2003-08-25 2:45 ` Takao Indoh
2003-08-25 4:11 ` William Lee Irwin III
2003-08-25 22:58 ` Mike Fedyk
2003-08-26 9:46 ` William Lee Irwin III
2003-08-27 9:36 ` Takao Indoh
2003-08-27 9:45 ` William Lee Irwin III
2003-08-27 11:14 ` Takao Indoh
2003-08-27 11:36 ` William Lee Irwin III
2003-09-02 10:52 ` Takao Indoh
2003-09-02 11:30 ` William Lee Irwin III
2003-09-02 17:21 ` Mike Fedyk
2003-08-27 16:01 ` Joseph Malicki
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=3F4B3352.4000703@softhome.net \
--to=filia@softhome.net \
--cc=indou.takao@soft.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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