From: Andrew Morton <akpm@osdl.org>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-dev@namesys.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Fix reiserfs latencies caused by data=ordered
Date: Fri, 4 Aug 2006 16:01:22 -0700 [thread overview]
Message-ID: <20060804160122.76d95426.akpm@osdl.org> (raw)
In-Reply-To: <20060804140708.GF1134@watt.suse.com>
On Fri, 4 Aug 2006 10:07:08 -0400
Chris Mason <mason@suse.com> wrote:
> ReiserFS does periodic cleanup of old transactions in order to limit the
> length of time a journal replay may take after a crash. Sometimes, writing
> metadata from an old (already committed) transaction may require committing
> a newer transaction, which also requires writing all data=ordered buffers.
> This can cause very long stalls on journal_begin.
>
> This patch makes sure new transactions will not need to be committed before
> trying a periodic reclaim of an old transaction. It is low risk because
> if a bad decision is made, it just means a slightly longer journal
> replay after a crash.
So I'm thinking that these:
i_mutex-does-not-need-to-be-locked-in-reiserfs_delete_inode.patch
fix-reiserfs-lock-inversion-of-bkl-vs-inode-semaphore.patch (akpm modified)
reiserfs_write_full_page-should-not-get_block-past-eof.patch
are 2.6.18 material. What are your thoughts on that?
next prev parent reply other threads:[~2006-08-04 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 14:07 [PATCH] Fix reiserfs latencies caused by data=ordered Chris Mason
2006-08-04 23:01 ` Andrew Morton [this message]
2006-08-07 12:20 ` Chris Mason
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=20060804160122.76d95426.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-dev@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;
as well as URLs for NNTP newsgroup(s).