From: David Newall <davidn@davidnewall.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: Zero length files - an alternative approach?
Date: Mon, 30 Mar 2009 06:46:42 +1030 [thread overview]
Message-ID: <49CFD72A.5010107@davidnewall.com> (raw)
In-Reply-To: <20090329134901.GB13737@elf.ucw.cz>
Pavel Machek wrote:
> fsync() is easy. But some people _want_ to have either newdata _or_
> olddata, but don't care which one, and would prefer to avoid
> fsync. That's where replace() should help...
Most people, I wager, care more about their code being portable than
they do about leaping through a Linux-specific hoop. They're not going
to use replace; not ever; that's what link/unlink is for.
If you think it's reasonable to modify every instance in applications
where a sudden crash would cause data loss, why not make a mount-time
flag that does all of that in FS; and for the other 99% of users, it
doesn't, but runs faster?
next prev parent reply other threads:[~2009-03-29 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 10:43 Zero length files - an alternative approach? Graham Murray
2009-03-29 11:22 ` Måns Rullgård
2009-03-29 12:02 ` Andreas T.Auer
2009-03-29 12:10 ` Måns Rullgård
2009-03-29 12:10 ` Måns Rullgård
2009-03-29 13:49 ` Pavel Machek
2009-03-29 20:16 ` David Newall [this message]
2009-03-30 12:41 ` Chris Mason
2009-03-30 12:41 ` Chris Mason
2009-03-30 14:06 ` Theodore Tso
2009-03-29 16:49 ` Avi Kivity
[not found] <cl0KI-3zZ-3@gated-at.bofh.it>
[not found] ` <cl1oA-4El-9@gated-at.bofh.it>
[not found] ` <clp6o-91-17@gated-at.bofh.it>
2009-03-30 21:10 ` Bodo Eggert
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=49CFD72A.5010107@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.