From: Chris Mason <mason@suse.com>
To: reiserfs-list@namesys.com, green@linuxhacker.ru
Subject: v3 experimental data=ordered and logging speedups for 2.6.1
Date: Mon, 19 Jan 2004 11:45:26 -0500 [thread overview]
Message-ID: <1074530725.29546.178.camel@tiny.suse.com> (raw)
Hello everyone,
I've got most of data=ordered finished, there are a few paths like
writepage and O_DIRECT that need tweaking. Thanks to Oleg's file_write
work in 2.6.x, the data=journal patch is much cleaner than 2.4, it is
almost done but not included in the bunch of patches I just uploaded to
ftp.suse.com. Oleg is cc'd in case he wants to look over the changes to
reiserfs_file_write in reiserfs-jh-2.
The code has survived a weekend of moderate load, but you still want it
very far away from production servers. I'm headed off to linux world in
NYC for the rest of the week, and I wanted to post this for review and
the few brave souls out there who might want to give it a try.
ftp.suse.com/pub/people/mason/patches/data-logging/experimental/2.6.1
The README:
Experimental reiserfs data=ordered and logging speedups against 2.6.1
Apply these in order:
01-reiserfs-journal-writer
removes old stale debugging code, very safe
02-reiserfs-nesting
Adds support for nested transactions in reiserfs, needed for the quota code,
and ported from 2.4.x by Jeff Mahoney
03-reiserfs-iosize
Changes reiserfs to tell userspace the default io size is 4k. Works around
a bug in bdb hit by rpm users
04-reiserfs-balance_dirty
Changes reiserfs_file_write to throttle writers the way the rest of linux
does. This patch has already been sent for inclusion, it should get in soon
05-reiserfs-logging
Logging speedups for small transactions and fsync heavy applications. Most
experimental patch of the bunch, since it changes the way the log does
metadata writeback
06-reiserfs-jh-2
Adds data=ordered support, along with a journal header attached to
the buffer head. This allows for more efficient data=ordered support
than I had in 2.4.x.
-chris
next reply other threads:[~2004-01-19 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 16:45 Chris Mason [this message]
2004-01-19 22:53 ` v3 experimental data=ordered and logging speedups for 2.6.1 Dieter Nützel
2004-01-19 22:54 ` Mike Fedyk
2004-01-21 1:50 ` Chris Mason
2004-02-09 13:04 ` Dieter Nützel
2004-02-09 14:14 ` Javier Marcet
2004-01-21 15:09 ` Oleg Drokin
2004-02-11 11:49 ` Oleg Drokin
2004-02-11 14:00 ` Chris Mason
2004-02-11 14:26 ` Oleg Drokin
2004-02-11 14:59 ` Chris Mason
2004-02-11 15:09 ` Oleg Drokin
2004-02-12 14:18 ` 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=1074530725.29546.178.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=green@linuxhacker.ru \
--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.