From: "Stephen C. Tweedie" <sct@redhat.com>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Theodore Tso <tytso@valinux.com>,
Andrew McNamara <andrewm@connect.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Ext2, fsync() and MTA's?
Date: Tue, 22 May 2001 17:57:59 +0100 [thread overview]
Message-ID: <20010522175759.S8080@redhat.com> (raw)
In-Reply-To: <20010522174825.Q8080@redhat.com> <Pine.LNX.4.30.0105221152400.19818-100000@waste.org>
In-Reply-To: <Pine.LNX.4.30.0105221152400.19818-100000@waste.org>; from oxymoron@waste.org on Tue, May 22, 2001 at 11:54:55AM -0500
Hi,
On Tue, May 22, 2001 at 11:54:55AM -0500, Oliver Xymoron wrote:
> > > > That's probably the right thing to add.
> > >
> > > I'd vote for an async flag instead.
> >
> > Why??? Why change the default behaviour to be something much slower?
>
> I was suggesting an async flag _in addition_ to the sync flag, both
> propagating to subdirs. Nice and orthogonal.
The whole problem is that the flag applies to both files and
directories, but we often only want it enforced on directories
(because we already have fsync for files). Adding another orthogonal
file+dir async flag won't help that at all.
Cheers,
Stephen
next prev parent reply other threads:[~2001-05-22 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-12 11:50 Ext2, fsync() and MTA's? Andrew McNamara
2001-05-12 14:13 ` Alan Cox
2001-05-12 14:53 ` Andrew McNamara
2001-05-12 15:20 ` Theodore Tso
2001-05-21 17:47 ` Stephen C. Tweedie
2001-05-21 22:04 ` Theodore Tso
2001-05-22 15:50 ` Oliver Xymoron
2001-05-22 16:48 ` Stephen C. Tweedie
2001-05-22 16:54 ` Oliver Xymoron
2001-05-22 16:57 ` Stephen C. Tweedie [this message]
2001-05-24 1:48 ` Marco d'Itri
2001-05-21 17:41 ` Stephen C. Tweedie
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=20010522175759.S8080@redhat.com \
--to=sct@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@connect.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
--cc=tytso@valinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox