All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Matthias Andree <ma+rfs@dt.e-technik.uni-dortmund.de>,
	reiserfs-list@namesys.com
Subject: Re: reiserfs3 and -o sync revisited
Date: 18 Nov 2002 09:11:36 -0500	[thread overview]
Message-ID: <1037628696.3392.4.camel@tiny> (raw)
In-Reply-To: <20021118111011.C3827@namesys.com>

On Mon, 2002-11-18 at 03:10, Oleg Drokin wrote:
> Hello!
> 
> On Fri, Nov 15, 2002 at 12:07:09PM +0100, Matthias Andree wrote:
> > I have reiserfs v3.6 (as of 2.4.19) with the following patches:
> > A-01-relocation-4.diff.gz
> > A-02-commit_super-9-relocation.diff.gz
> > A-03-data-logging-25.diff.gz
> > A-03-logging-export.diff.gz
> > A-04-write_times.diff.gz
> > A-05-search_reada-4.diff.gz
> 
> > The A and B patches are Chris Mason's and the official Namesys patches,
> > possibly gzipped, the rest does not touch ReiserFS code except possibly
> > rmap.
> > I have run some bonnie++ 1.02c tests on an old swap partition I
> > converted to reiserfs, ext3fs or ext2fs, and I gather that using the
> > mount -o sync option makes virtually no difference on reiserfs, but
> > brings ext3 and ext2 nearly to a halt. Is mount -o sync implemented and
> > working?
> 
> -o sync is implemented by VFS.
> I remember that some early implementation of data logging patches have broken
> sync behaviour and reiserfs got huge boost in some tests ;) )
> I do not know which version of the patches you aer using, though.
> 
> Chris, do your latest patches fix that sync problem?

-o sync needs a little help from the filesystem, and my patches don't
add it.  Since we support fsync(file) after rename triggering a commit
on the rename, we don't really need -o sync.

But yes, I did fix my O_SYNC/fsync bug in the early versions of the data
logging patches ;-)

-chris



  reply	other threads:[~2002-11-18 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 11:07 reiserfs3 and -o sync revisited Matthias Andree
2002-11-18  8:10 ` Oleg Drokin
2002-11-18 14:11   ` Chris Mason [this message]
2002-11-19 16:34     ` Matthias Andree

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=1037628696.3392.4.camel@tiny \
    --to=mason@suse.com \
    --cc=green@namesys.com \
    --cc=ma+rfs@dt.e-technik.uni-dortmund.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.