From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: kernel BUG at buffer.c:827 in test12-pre6 and 7
Date: Fri, 08 Dec 2000 14:22:27 -0800 [thread overview]
Message-ID: <3A315F23.6110A7CD@sgi.com> (raw)
In-Reply-To: <90rjbg$8eso1$1@fido.engr.sgi.com>
Linus Torvalds wrote:
>
> On Fri, 8 Dec 2000, Daniel Phillips wrote:
> >
> > [ flush-buffers taking the page lock ]
> >
> > This is great when you have buffersize==pagesize. When there are
> > multiple buffers per page it means that some of the buffers might have
> > to wait for flushing just because bdflush started IO on some other
> > buffer on the same page. Oh well. The common case improves in terms
> > being proveably correct and the uncommon case gets worse a tiny bit.
> > It sounds like a win.
>
> Also, I think that we should strive for a setup where most of the dirty
> buffer flushing is done through "page_launder()" instead of using
> sync_buffers all that much at all.
>
> I'm convinced that the page LRU list is as least as good as, if not better
> than, the dirty buffer timestamp stuff. And as we need to have the page
> LRU for other reasons anyway, I'd like the long-range plan to be to get
> rid of the buffer LRU completely. It wastes memory and increases
> complexity for very little gain, I think.
>
I think flushing pages instead of buffers is a good direction to take.
Two things:
1. currently bdflush is setup to use page_launder only
under memory pressure (if (free_shortage() ... )
Do you think that it should call page_launder regardless?
2. There are two operations here:
a. starting a write-back, periodically.
b. freeing a page, which may involve taking the page
out of a inode mapping, etc. IOW, what page_launder does.
bdflush primarily does (a). If we want to move to page-oriented
flushing, we atleast need extra information in the _page_ structure
as to whether it is time to flush the page back.
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-12-08 22:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <90rjbg$8eso1$1@fido.engr.sgi.com>
2000-12-08 22:22 ` Rajagopal Ananthanarayanan [this message]
2000-12-08 9:58 [found?] Re: kernel BUG at buffer.c:827 in test12-pre6 and 7 Alexander Viro
2000-12-08 18:11 ` [PATCH] " Alexander Viro
2000-12-08 18:48 ` Linus Torvalds
2000-12-08 19:13 ` Alexander Viro
2000-12-08 19:39 ` Linus Torvalds
2000-12-08 19:50 ` Daniel Phillips
2000-12-08 21:17 ` Linus Torvalds
2000-12-08 22:30 ` Alexander Viro
2000-12-08 22:42 ` Linus Torvalds
2000-12-09 4:59 ` Alexander Viro
2000-12-09 8:45 ` Linus Torvalds
2000-12-09 8:56 ` Linus Torvalds
2000-12-09 10:40 ` Alexander Viro
2000-12-09 12:56 ` Andries Brouwer
2000-12-09 13:11 ` Alexander Viro
2000-12-09 21:25 ` Mikulas Patocka
2000-12-10 1:11 ` Linus Torvalds
2000-12-09 17:28 ` Linus Torvalds
2000-12-09 18:43 ` Andi Kleen
2000-12-09 14:00 ` David S. Miller
2000-12-09 15:37 ` David Woodhouse
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=3A315F23.6110A7CD@sgi.com \
--to=ananth@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.