From: Chris Mason <mason@suse.com>
To: reiserfs-list@namesys.com
Subject: Re: udpated data logging available
Date: 22 Jun 2003 22:45:43 -0400 [thread overview]
Message-ID: <1056336342.5545.376.camel@tiny.suse.com> (raw)
In-Reply-To: <1055944613.5545.22.camel@tiny.suse.com>
On Wed, 2003-06-18 at 09:56, Chris Mason wrote:
> Hello again,
>
> ftp.suse.com/pub/people/mason/patches/data-logging/2.4.21/experimental
>
> Has two additional patches. The first is io-stalls-logging-6.diff,
> which is very similar to the io stalling code I've been posting on the
> linux kernel list. It's unrelated to reiserfs really, and fixes some
> fairness issues at the block device layer.
>
> The second is reiserfs-jh-1, which changes where the lists live for
> data=ordered and tail buffers. It allows us to do a few things:
Hello all, I've updated the reiserfs-jh patch, it's now at
reiserfs-jh-2. The major changes are tested O_DIRECT + data=ordered
support, and a bug fix for an oops under memory pressure.
In general the patch has had a few more hours of testing on it now, and
I'm less worried about it making your computer catch on fire if you give
it a try.
-chris
next prev parent reply other threads:[~2003-06-23 2:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 11:47 udpated data logging available Chris Mason
2003-06-18 13:56 ` Chris Mason
2003-06-23 2:45 ` Chris Mason [this message]
2003-06-23 16:53 ` Christian Mayrhuber
2003-06-25 19:15 ` Chris Mason
2003-06-26 0:16 ` Christian Mayrhuber
2003-06-26 1:47 ` Chris Mason
2003-06-26 11:42 ` Dieter Nützel
2003-06-26 12:53 ` Chris Mason
2003-06-26 13:36 ` Manuel Krause
2003-07-01 23:41 ` Manuel Krause
2003-07-02 1:44 ` Chris Mason
2003-06-26 17:19 ` Dieter Nützel
2003-07-02 0:46 ` Manuel Krause
2003-07-02 1:46 ` Chris Mason
2003-06-26 11:48 ` Dieter Nützel
2003-06-26 12:18 ` Philippe Gramoullé
2003-06-26 12:35 ` 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=1056336342.5545.376.camel@tiny.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.