From: David Ford <david@linux.com>
To: Chris Mason <mason@suse.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 15:42:37 -0800 [thread overview]
Message-ID: <3A79F46D.24B0A201@linux.com> (raw)
In-Reply-To: <371620000.981044164@tiny>
Chris Mason wrote:
> 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
(http://208.179.0.18/VM/)
[schedule_timeout+115/148] [process_timeout+0/72] [interruptible_sleep_on_timeout+66/92] [reiserfs_journal_commit_thread+173/224] [kernel_thread+40/56]
-d
--
There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum
-
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 23:43 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 ` David Ford [this message]
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-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=3A79F46D.24B0A201@linux.com \
--to=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox