All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: reiserfs-list@namesys.com
Subject: Re: v3 logging speedups for 2.6
Date: Thu, 11 Dec 2003 13:42:39 -0500	[thread overview]
Message-ID: <1071168158.10849.131.camel@tiny.suse.com> (raw)
In-Reply-To: <200312111930.49910.Dieter.Nuetzel@hamburg.de>

On Thu, 2003-12-11 at 13:30, Dieter Nützel wrote:
> Am Donnerstag, 11. Dezember 2003 19:10 schrieb Chris Mason:
> > Hello everyone,
> >
> > This is part one of the data logging port to 2.6, it includes all the
> > cleanups and journal performance fixes.  Basically, it's everything
> > except the data=journal and data=ordered changes.
> >
> > The 2.6 merge has a few new things as well, I've changed things around
> > so that metadata and log blocks will go onto the system dirty lists.
> > This should make it easier to improve log performance, since most of the
> > work will be done outside the journal locks.
> >
> > The code works for me, but should be considered highly experimental.  In
> > general, it is significantly faster than vanilla 2.6.0-test11, I've done
> > tests with dbench, iozone, synctest and a few others.  streaming writes
> > didn't see much improvement (they were already at disk speeds), but most
> > other tests did.
> >
> > Anyway, for the truly daring among you:
> >
> > ftp.suse.com/pub/people/mason/patches/data-logging/experimental/2.6.0-test11
> >
> > The more bug reports I get now, the faster I'll be able to stabilize
> > things.  Get the latest reiserfsck and check your disks after each use.
> 
> Chris,
> 
> with which kernel should I start on my SuSE 9.0?
> A special SuSE 2.6.0-test11 + data logging?
> Or plane native? --- There are such much patches in SuSE kernels...

For the moment you can only try it on vanilla 2.6.0-test11.   The suse
2.6 rpms have acls/xattrs and the new logging stuff won't apply.

Jeff and I will fix that when the logging merge is really complete.  At
the rate I'm going, that should be by the end of next week, this part of
the merge was the really tricky bits.

-chris



  reply	other threads:[~2003-12-11 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 18:10 v3 logging speedups for 2.6 Chris Mason
2003-12-11 18:30 ` Dieter Nützel
2003-12-11 18:42   ` Chris Mason [this message]
2004-01-12 20:08     ` Dieter Nützel
2004-01-12 20:33       ` Dieter Nützel
     [not found] ` <2652990.fVlIM9mB2a@spamfreemail.de>
2004-01-12 14:57   ` Chris Mason
2004-01-14 12:47     ` Jens Benecke

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=1071168158.10849.131.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --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.