From: Andrew Morton <akpm@zip.com.au>
To: "Peter J. Braam" <braam@clusterfs.com>,
Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [patch 11/18] dirsync
Date: Sun, 26 May 2002 14:54:17 -0700 [thread overview]
Message-ID: <3CF15989.D6AA332C@zip.com.au> (raw)
In-Reply-To: <3CF14973.B61EF771@zip.com.au> <20020526093637.V32110@lustre.cfs> <3CF15838.FE768070@zip.com.au>
Andrew Morton wrote:
>
> "Peter J. Braam" wrote:
> >
> > Hi
> >
> > I think this patch is actually pretty important - could we please have
> > this, or something like this?
> >
>
> Well `-o sync' will give the same result. dirsync is just a speedup.
>
> I should have mentioned: untarring a kernel tree with dirsync is 4x to
> 5x faster than `-o sync', but still tons slower (5x?) than default.
grr. On ext2.
On ext3, dirsync _is_ sync for journalled and ordered modes. If you
run a commit, you sync the entire fs, end of story. So dirsync on ext3
really only makes a difference in writeback mode.
-
prev parent reply other threads:[~2002-05-26 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 20:45 [patch 11/18] dirsync Andrew Morton
2002-05-26 15:36 ` [Ext2-devel] " Peter J. Braam
2002-05-26 21:48 ` Andrew Morton
2002-05-26 21:54 ` Andrew Morton [this message]
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=3CF15989.D6AA332C@zip.com.au \
--to=akpm@zip.com.au \
--cc=braam@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.