From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: Zlatko.Calusic@CARNet.hr
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <H.H.vanRiel@phys.uu.nl>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] swapin readahead
Date: 02 Dec 1998 23:25:38 -0600 [thread overview]
Message-ID: <m1af15iyp9.fsf@flinx.ccr.net> (raw)
In-Reply-To: Zlatko Calusic's message of "02 Dec 1998 22:18:58 +0100"
>>>>> "ZC" == Zlatko Calusic <Zlatko.Calusic@CARNet.hr> writes:
ZC> Trying 2.1.131-2, I'm mostly satisfied with MM workout, but...
ZC> Still, I have a feeling that limit imposed on cache growth is now too
ZC> hard, unlike kernels from the 2.1.1[01]? era, that had opposite
ZC> problems (excessive cache growth during voluminous I/O operations).
My gut reaction is that we need a check in swap_out to see if we have
written out a swap_cluster or some other indication that we have
started all of the disk i/o that is reasonable for now and need to
switch to something else.
This should have the same effect as the switches with the limits on
the swap cache but more autobalancing. I'm nervous of a kernel that
needs small limits on it's disk cache to work correctly.
ZC> What I wanted to ask is: do you guys share my opinion, and what
ZC> changes would you like to see before 2.2 comes out?
One thing worth putting in. Probably before to 2.2 but definentily
before any swap page readahead is done is to start using brw_page
for swapfiles. I don't know about synchronous cases, but in the when
asynchronous operation is important it improves swapfile performance
immensely.
Eric
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-12-03 6:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-26 23:23 Rik van Riel
1998-12-01 15:13 ` Stephen C. Tweedie
1998-12-01 15:41 ` Rik van Riel
1998-12-01 15:51 ` Zlatko Calusic
1998-12-01 16:42 ` Rik van Riel
1998-12-01 17:20 ` Zlatko Calusic
1998-12-01 18:32 ` Rik van Riel
1998-12-02 17:35 ` Stephen C. Tweedie
1998-12-02 21:18 ` Zlatko Calusic
1998-12-03 5:25 ` Eric W. Biederman [this message]
1998-12-03 8:55 ` Zlatko Calusic
1998-12-03 15:39 ` Eric W. Biederman
1998-12-03 10:07 ` Rik van Riel
1998-12-02 17:33 ` Stephen C. Tweedie
1998-12-03 14:44 ` Rik van Riel
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=m1af15iyp9.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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