From: Theodore Tso <tytso@mit.edu>
To: Roger Larsson <roger.larsson@norran.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] Copy on First Read?
Date: Mon, 10 Jul 2006 13:59:27 -0400 [thread overview]
Message-ID: <20060710175927.GA16137@thunk.org> (raw)
In-Reply-To: <200607101225.46928.roger.larsson@norran.net>
On Mon, Jul 10, 2006 at 12:25:46PM +0200, Roger Larsson wrote:
> Not double since it is only the first read after a write that needs to be
> rewritten. My assumption is that most files are written fewer times than
> they are read. And the read for the copy is free since that was what
> triggered it.
But there is a cost, and the question is how much does this buy you
compared to simply getting it right the first time, either via a
delayed allocation scheme, or where the application knows how big the
file is up front (as is often the case).
In addition your scheme is extremely pessimal behaviour for temporary
files which are writtena and read once before being deleted....
- Ted
next prev parent reply other threads:[~2006-07-10 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 7:04 [RFC] Copy on First Read? Roger Larsson
2006-07-10 8:27 ` Andreas Dilger
2006-07-10 10:25 ` Roger Larsson
2006-07-10 17:59 ` Theodore Tso [this message]
2006-07-10 20:42 ` Roger Larsson
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=20060710175927.GA16137@thunk.org \
--to=tytso@mit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=roger.larsson@norran.net \
/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