From: Chris Mason <mason@suse.com>
To: Rik van Riel <riel@conectiva.com.br>, David Ford <david@linux.com>
Cc: LKML <linux-kernel@vger.kernel.org>, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] Re: VM brokenness, possibly related to reiserfs
Date: Thu, 01 Feb 2001 11:31:42 -0500 [thread overview]
Message-ID: <377430000.981045102@tiny> (raw)
In-Reply-To: <Pine.LNX.4.21.0102011411540.1321-100000@duckman.distro.conectiva>
On Thursday, February 01, 2001 02:16:43 PM -0200 Rik van Riel <riel@conectiva.com.br> wrote:
>
> About the system hanging completely, I wonder if it goes
> away by pressing sysrq-S (sync all disks). If it does,
> maybe Reiserfs was blocking all the pages in the inactive
> list from being written because one of the active pages
> (not a replacement candidate) needed to be written out
> first? Or does the Reiserfs ->writepage() function handle
> this?
>
In most cases, the reiserfs writepage func is the same as block_write_full_page. The only difference should come when a packed tail has been mmap'd.
Since JOURNAL_MAX_BATCH was at 100, the log should have only pinned 400k. More blocks could be pinned, but kreiserfsd should be in the process of flushing those.
I've been trying out a few things to send memory pressure down to reiserfs, but they have mostly been based on the code to make fs/buffer.c use writepage for flushing. I should have done something simple first, I'll start on that now.
-chris
-
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 prev parent reply other threads:[~2001-02-01 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 7:02 VM brokenness, possibly related to reiserfs David Ford
2001-02-01 16:16 ` Chris Mason
2001-02-01 23:42 ` [reiserfs-list] " David Ford
2001-02-01 16:16 ` Rik van Riel
2001-02-01 16:31 ` Chris Mason [this message]
2001-02-01 23:05 ` [reiserfs-list] " David Ford
2001-02-04 0:45 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 0:05 David Ford
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=377430000.981045102@tiny \
--to=mason@suse.com \
--cc=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=riel@conectiva.com.br \
/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