From: Chris Mason <mason@suse.com>
To: David Ford <david@linux.com>, LKML <linux-kernel@vger.kernel.org>,
reiserfs-list@namesys.com
Subject: Re: VM brokenness, possibly related to reiserfs
Date: Thu, 01 Feb 2001 11:16:04 -0500 [thread overview]
Message-ID: <371620000.981044164@tiny> (raw)
In-Reply-To: <3A790A16.C964877@linux.com>
On Wednesday, January 31, 2001 11:02:46 PM -0800 David Ford <david@linux.com> wrote:
> (Chris, changing JOURNAL_MAX_BATCH from 900 to 100 didn't affect
> anything).
>
> Ok, having approached this slightly more intelligently here are [better]
> results.
>
> The dumps are large so they are located at http://stuph.org/VM/. Here's
> the story.
Sorry, can't seem to resolve stuph.org. What is kreiserfsd doing during when the system is waiting for more ram? With JOURNAL_MAX_BATCH set to 100, kreiserfsd will end up responsible for sending log blocks/metadata to disk and freeing the pinned buffers.
-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:16 UTC|newest]
Thread overview: 10+ 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 [this message]
2001-02-01 23:42 ` [reiserfs-list] " David Ford
2001-02-01 16:16 ` Rik van Riel
2001-02-01 16:31 ` [reiserfs-list] " Chris Mason
2001-02-01 23:05 ` David Ford
2001-02-04 0:45 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 12:39 Ed Tomlinson
2001-02-01 12:43 ` David Ford
2001-02-01 16:29 ` Rik van Riel
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=371620000.981044164@tiny \
--to=mason@suse.com \
--cc=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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.