From: Manuel Krause <manuelkrause@netscape.net>
To: Chris Mason <mason@suse.com>, Oleg Drokin <green@namesys.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: data-logging for 2.4.21+ (was Re: How to build a big file server)
Date: Sat, 14 Jun 2003 13:11:31 +0200 [thread overview]
Message-ID: <3EEB02E3.6030608@netscape.net> (raw)
In-Reply-To: 1054820922.23132.133.camel@tiny.suse.com
On 06/05/2003 03:48 PM, Chris Mason wrote:
> On Thu, 2003-06-05 at 06:25, Russell Coker wrote:
>
>
>>>I use SuSE 8.2. It's much faster than the SuSE kernel in 8.1, even on my
>>>ZIP drive at the parallel port ;)
>>
>>Hopefully someone can advise on whether the SuSE 8.2 kernel has all the
>>patches you desire for best ReiserFS performance.
>
>
> The suse kernels include the data logging code, along with the other
> minor optimizations in my data logging dir.
>
> The good news is that I've also tracked down a long standing
> data=ordered performance bug, and I've got more data=ordered
> optimizations to make fsync workloads better. Hopefully this morning I
> can get it all to stop oopsing and I'll send out for broader testing.
>
> -chris
Hi, Chris, Oleg and all others!
Are these patches ready for "broader testing" now? I would appreciate it
as you mentioned the key words "performance" and "data=ordered" in one
sentence ... ;-))
Does the iget5_locked patch (Oleg?!) get updated or is it obsolete? It
didn't apply fine to 2.4.21-pre6. So I skipped it for that kernel.
I didn't try kernels > 2.4.21-pre6 so far -- my simple question is: Are
the new patches in the queue or have they been forgotten over time? Or
are there some compounds or merges in progress?!!
Many thanks for clarification,
best regards,
Manuel
next prev parent reply other threads:[~2003-06-14 11:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 8:14 How to build a big file server Heinz-Josef Claes
2003-06-05 8:25 ` Carl-Daniel Hailfinger
2003-06-05 8:55 ` Andreas Dilger
2003-06-05 9:51 ` Hendrik Visage
2003-06-05 8:33 ` Ragnar Kjørstad
2003-06-05 8:42 ` Heinz-Josef Claes
2003-06-05 8:45 ` Marc-Christian Petersen
2003-06-05 9:30 ` Heinz-Josef Claes
2003-06-05 11:27 ` Bill Rees
2003-06-10 13:28 ` myciel
2003-06-10 13:36 ` Heinz-Josef Claes
2003-06-10 14:13 ` myciel
2003-06-12 20:34 ` Lars O. Grobe
2003-06-05 8:46 ` Oleg Drokin
2003-06-05 8:50 ` Heinz-Josef Claes
2003-06-05 9:04 ` Oleg Drokin
2003-06-05 9:17 ` Heinz-Josef Claes
2003-06-05 10:29 ` Russell Coker
2003-06-05 10:45 ` Heinz-Josef Claes
2003-06-05 16:47 ` Carl-Daniel Hailfinger
2003-06-05 17:01 ` Soeren Sonnenburg
2003-06-05 17:06 ` Ragnar Kjørstad
2003-06-06 9:41 ` Heinz-Josef Claes
2003-06-05 13:38 ` Hans Reiser
2003-06-05 12:06 ` Heinz-Josef Claes
2003-06-05 9:45 ` Christophe Saout
2003-06-05 10:07 ` Soeren Sonnenburg
2003-06-05 9:59 ` Russell Coker
2003-06-05 10:13 ` Heinz-Josef Claes
2003-06-05 10:25 ` Russell Coker
2003-06-05 10:38 ` Heinz-Josef Claes
2003-06-05 11:11 ` Russell Coker
2003-06-05 13:48 ` Chris Mason
2003-06-14 11:11 ` Manuel Krause [this message]
2003-06-05 10:05 ` Hans Reiser
2003-06-05 10:24 ` Heinz-Josef Claes
2003-06-05 13:43 ` Sam Vilain
2003-06-05 13:55 ` Heinz-Josef Claes
2003-06-06 11:15 ` Vitezslav T. Se'm
2003-06-06 15:15 ` Russell Coker
2003-06-06 11:16 ` Vitezslav T. Se'm
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=3EEB02E3.6030608@netscape.net \
--to=manuelkrause@netscape.net \
--cc=green@namesys.com \
--cc=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.