From: Rik van Riel <riel@conectiva.com.br>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-mm@kvack.org, Linus Torvalds <torvalds@transmeta.com>,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [highmem bug report against -test5 and -test6] Re: [PATCH] Re: simple FS application that hangs 2.4-test5, mem mgmt problem or FS buffer cache mgmt problem? (fwd)
Date: Mon, 2 Oct 2000 17:24:44 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010021722440.1067-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20001002221718.B21995@athlon.random>
On Mon, 2 Oct 2000, Andrea Arcangeli wrote:
> On Mon, Oct 02, 2000 at 04:59:57PM -0300, Rik van Riel wrote:
> > Linus, I remember you saying some time ago that you would
> > like to keep the buffer heads on a page around so we'd
> > have them at the point where we need to swap out again.
>
> That's one of the basic differences between the 2.2.x and 2.4.x
> page cache design. We don't reclaim the buffers at I/O completion
> time anymore in 2.4.x but we reclaim them only later when we run
> low on memory.
>
> Forbidding the bh to be reclaimed when we run low on memory is a
> bug and I don't think Linus ever suggested that.
*nod*
How about having the following code in refill_inactive_scan() ?
if (page->buffers && page->mapping)
try_to_free_buffers(page, 0);
(this will strip the buffer heads of any clean page cache
page ... we don't want to strip buffer head pages because
that would mean throwing away the data from that page)
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-10-02 20:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 19:35 Rik van Riel
2000-10-02 19:56 ` Andrea Arcangeli
2000-10-02 19:59 ` Rik van Riel
2000-10-02 20:17 ` Andrea Arcangeli
2000-10-02 20:24 ` Rik van Riel [this message]
2000-10-02 21:16 ` Linus Torvalds
2000-10-02 20:06 ` Linus Torvalds
2000-10-02 20:16 ` Rik van Riel
2000-10-02 20:25 ` Ingo Molnar
2000-10-02 20:45 ` Rik van Riel
2000-10-02 21:21 ` Linus Torvalds
2000-10-02 21:27 ` Rik van Riel
2000-10-02 21:19 ` Linus Torvalds
2000-10-02 21:23 ` Rik van Riel
2000-10-02 21:31 ` Linus Torvalds
2000-10-02 21:42 ` Rik van Riel
2000-10-02 21:58 ` Linus Torvalds
2000-10-02 22:08 ` Rik van Riel
2000-10-02 22:18 ` Andrea Arcangeli
2000-10-02 22:23 ` Rik van Riel
2000-10-02 23:06 ` Linus Torvalds
2000-10-02 23:12 ` Rik van Riel
2000-10-02 23:16 ` Linus Torvalds
2000-10-02 23:20 ` Andrea Arcangeli
2000-10-02 22:53 ` Linus Torvalds
2000-10-02 23:06 ` Rik van Riel
2000-10-02 23:14 ` Linus Torvalds
2000-10-02 21:57 ` Ingo Molnar
2000-10-02 21:52 ` Rik van Riel
2000-10-02 22:53 ` Ingo Molnar
2000-10-02 23:01 ` Rik van Riel
2000-10-02 23:10 ` Andrea Arcangeli
2000-10-02 23:29 ` Ingo Molnar
2000-10-02 23:25 ` Andrea Arcangeli
2000-10-02 23:32 ` Linus Torvalds
2000-10-03 12:05 ` Ingo Molnar
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.21.0010021722440.1067-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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