From: Ingo Molnar <mingo@elte.hu>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andrea Arcangeli <andrea@suse.de>,
MM mailing list <linux-mm@kvack.org>,
"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: Tue, 3 Oct 2000 01:29:27 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010030127050.17037-100000@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.21.0010021956410.1067-100000@duckman.distro.conectiva>
On Mon, 2 Oct 2000, Rik van Riel wrote:
> > > > another thing is the complexity of marking a page dirty - right
> > > > now we can assume that page->buffers holds all the blocks. With
> > > > aging we must check wether a bh is there or not,
> > >
> > > The code must already be able to handle this. This is nothing new.
> >
> > sure this is new. The page->buffers list right now is assumed to
> > stay constant after being created.
>
> Eeeeeek. So pages /cannot/ lose their buffer heads ???
it can and does lose them - but only all of them. Aging OTOH is a per-bh
thing, this kind of granularity is simply not present in the current
page->buffers handling. This is all i wanted to mention. Not unsolvable,
but needs extra logic.
Ingo
--
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 23:29 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
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 [this message]
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.0010030127050.17037-100000@elte.hu \
--to=mingo@elte.hu \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--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