From: Rik van Riel <riel@conectiva.com.br>
To: marc heckmann <heckmann@hbesoftware.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.4.8-pre7: still buffer cache problems
Date: Thu, 9 Aug 2001 17:55:59 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0108091749580.1439-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <32774.213.7.60.90.997365391.squirrel@webmail.hbesoftware.com>
On Thu, 9 Aug 2001, marc heckmann wrote:
> While 2.4.8-pre7 definitely fixes the "dd if=/dev/zero
> of=bigfile bs=1000k count=bignumber" case. The "dd if=/dev/hda
> of=/dev/null" is still quite broken for me.
OK, there is no obvious way to do do drop-behind on
buffer cache pages, but I think we can use a quick
hack to make the system behave well under the presence
of large amounts of buffer cache pages.
What we could do is, in refill_inactive_scan(), just
moving buffer cache pages to the inactive list regardless
of page aging when there are too many buffercache pages
around in the system.
Does the patch below help you ?
regards,
Rik
--
IA64: a worthy successor to the i860.
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com/
--- linux-2.4.7-ac7/mm/vmscan.c.buffer Thu Aug 9 17:54:24 2001
+++ linux-2.4.7-ac7/mm/vmscan.c Thu Aug 9 17:55:09 2001
@@ -708,6 +708,8 @@
* This function will scan a portion of the active list to find
* unused pages, those pages will then be moved to the inactive list.
*/
+#define too_many_buffers (atomic_read(&buffermem_pages) > \
+ (num_physpages * buffer_mem.borrow_percent / 100))
int refill_inactive_scan(zone_t *zone, unsigned int priority, int target)
{
struct list_head * page_lru;
@@ -770,6 +772,18 @@
page_active = 1;
}
}
+
+ /*
+ * If the amount of buffer cache pages is too
+ * high we just move every buffer cache page we
+ * find to the inactive list. Eventually they'll
+ * be reclaimed there...
+ */
+ if (page->buffers && !page->mapping && too_many_buffers) {
+ deactivate_page_nolock(page);
+ page_active = 0;
+ }
+
/*
* If the page is still on the active list, move it
* to the other end of the list. Otherwise we exit if
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-08-09 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 13:56 marc heckmann
2001-08-09 16:09 ` Chris Mason
2001-08-09 20:55 ` Rik van Riel [this message]
2001-08-10 0:20 ` marc heckmann
2001-08-15 11:06 ` 2.4.8-pre7: still buffer cache problems[+2.4.9-pre3 comments] Marc Heckmann
2001-08-10 1:52 ` 2.4.8-pre7: still buffer cache problems Ed Tomlinson
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=Pine.LNX.4.33L.0108091749580.1439-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=heckmann@hbesoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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