All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Re: [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1
Date: Tue, 08 Oct 2002 22:31:46 +0200	[thread overview]
Message-ID: <3DA340B2.5000605@mb.tu-ilmenau.de> (raw)
In-Reply-To: 1033996342.13900.383.camel@tiny

On 10/07/2002 03:12 PM, Chris Mason wrote:
> On Fri, 2002-10-04 at 18:01, Andreas Dilger wrote:
> 
>>On Oct 04, 2002  22:54 +0200, Dieter N?tzel wrote:
>>
>>>Am Mittwoch, 2. Oktober 2002 10:48 schrieb Paul P Komkoff Jr:
>>>
[...]
> 
> The data logging patches have a bunch of other metadata writeback
> optimizations.  It helps most for small transactions, but improves
> things for all metadata workloads.  Updated 2.4.20-preX patches should
> finally go out today, and then I'll start on 2.5
                  ^^^^^                                   ?

Sorry, Chris & list!

Somehow, I don't like these kinds of announcements<->reality relation 
@reiserfs-list until now. These patches have been announced 2 weeks ago 
already, IIRC.

Mmh. If I didn't follow my announced timelines, I would keep getting 
serious problems here... ;-)  How Do _you_ solve this? Any hints?!


But, best wishes for your "hidden" work, Chris, I still believe...

Manuel


  reply	other threads:[~2002-10-08 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 20:54 [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1 Dieter Nützel
2002-10-04 21:28 ` 2.5.40 (was " Valdis.Kletnieks
2002-10-04 21:54   ` Ed Tomlinson
2002-10-04 22:21     ` Valdis.Kletnieks
2002-10-04 22:00   ` Andreas Dilger
2002-10-04 22:01 ` Re: [STUPID TESTCASE] " Andreas Dilger
2002-10-07  8:51   ` Oleg Drokin
2002-10-07 13:12   ` Chris Mason
2002-10-08 20:31     ` Manuel Krause [this message]
2002-10-04 22:27 ` Hans Reiser

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=3DA340B2.5000605@mb.tu-ilmenau.de \
    --to=manuel.krause@mb.tu-ilmenau.de \
    --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.