From: Chris Mason <mason@suse.com>
To: reiserfs-list@namesys.com
Subject: [PATCH] updated data=ordered patch for 2.6.3
Date: Wed, 18 Feb 2004 23:36:13 -0500 [thread overview]
Message-ID: <1077165373.22253.45.camel@watt.suse.com> (raw)
Hello everyone,
I've updated the reiserfs logging speedups and data=ordered support to
2.6.3, and fixed a few bugs:
i_block count not properly updated on files with holes
oops when the disk is full
small files were not being packed into tails
Also, the code has some extra performance tweaks to smooth out
performance both with and without data=ordered. There are new
mechanisms to trigger metadata/commit block writeback and to help
throttle writers. The goal is to reduce the huge bursts of io during a
commit and during data=ordered writeback.
I'm very interested in benchmarks here and info about how the patches
feel for interactive performance.
Please note that data=ordered is not the default yet, you have to mount
with -o data=ordered to get it.
You can get the patches from:
ftp.suse.com/pub/people/mason/patches/data-logging/experimental/2.6.3
(once the suse mirror copies it over there)
-chris
next reply other threads:[~2004-02-19 4:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 4:36 Chris Mason [this message]
2004-02-23 9:42 ` [PATCH] updated data=ordered patch for 2.6.3 Dieter Nützel
2004-02-23 19:11 ` Chris Mason
2004-02-23 19:35 ` Vince
2004-03-01 13:30 ` Christophe Saout
2004-03-01 14:01 ` Chris Mason
[not found] ` <1078151441.7036.2.camel@leto.cs.pocnet.net>
2004-03-01 14:38 ` Chris Mason
2004-03-01 15:41 ` Dieter Nützel
2004-03-02 18:14 ` Dieter Nützel
2004-03-02 18:16 ` Chris Mason
2004-03-02 18:22 ` Dieter Nützel
2004-03-02 19:53 ` Dieter Nützel
2004-03-02 20:06 ` Chris Mason
2004-03-02 21:06 ` Dieter Nützel
2004-03-02 21:48 ` Dieter Nützel
2004-03-03 2:12 ` Chris Mason
2004-03-03 9:13 ` Marc-Christian Petersen
2004-03-03 22:13 ` Dieter Nützel
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=1077165373.22253.45.camel@watt.suse.com \
--to=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 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.