From: Chris Mason <mason@suse.com>
To: Jens Benecke <jens-usenet@spamfreemail.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Chris: mason/patches/data-logging/experimental/2.6.1 upside down?
Date: Tue, 13 Jan 2004 23:11:42 -0500 [thread overview]
Message-ID: <1074053501.32707.995.camel@tiny.suse.com> (raw)
In-Reply-To: <31592854.1BIkuMAj52@spamfreemail.de>
On Tue, 2004-01-13 at 17:13, Jens Benecke wrote:
> Dieter Nützel wrote:
>
> > See this, too.
> > Re: v3 logging speedups for 2.6
> > It's (SuSE 9.0 2.6.1) is running fine with reiserfs-journal-writer.
>
> I'll have a look.
>
> What exactly do experimental/2.6.1/journal-writer and logging.gz do /
> change / update? How experimental are they?
>
journal-writer isn't experimental at all, it just removes old debugging
code. reiserfs-logging.gz is the first half of the 2.4.x data logging
code. Basically the 2.4.x data logging patch had two parts, the first
part made small transactions significantly more efficient, and the
second part implemented data=ordered/data=journal.
So, reiserfs-logging.gz has the small transaction performance
improvements, along with some other rewrites of how log blocks and
metadata get to disk. In 2.4.x and vanilla 2.6, reiserfs keeps log
blocks and metadata pinned and then writes them out at very specific
times. The new code keeps them pinned until they are safe to write, but
lets the system pdflush daemons do some of the writeback.
This makes for smoother io overall, since things aren't done in bursts.
-chris
next prev parent reply other threads:[~2004-01-14 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3171912.lEEDWjxvxS@spamfreemail.de>
2004-01-13 21:47 ` Chris: mason/patches/data-logging/experimental/2.6.1 upside down? Dieter Nützel
[not found] ` <31592854.1BIkuMAj52@spamfreemail.de>
2004-01-14 4:11 ` Chris Mason [this message]
2004-01-13 21:56 ` 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=1074053501.32707.995.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=jens-usenet@spamfreemail.de \
--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.