public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@norran.net>
To: linux-fsdevel@vger.kernel.org
Subject: [RFC] Copy on First Read?
Date: Mon, 10 Jul 2006 09:04:44 +0200	[thread overview]
Message-ID: <200607100904.44983.roger.larsson@norran.net> (raw)

I have been thinking about a file system that uses Copy On First Read.
My idea looks like this:

1. Split the disk in three parts (unused, write, used - could be growing from 
top and bottom like heap and stack)
2. Writes goes to one part - log structured, like a tape. Fragmentation of 
files are OK, but buffering is done to prevent the worst cases.

This to allow fast write of huge amounts of data.

Later when the file is first read
* the size is known.
* is probably read together with other files that in future will be used
   together.

So the allocation rule for the copy on first read can use these facts.
Only files that are actually used will be read and thus rewritten.

This will leave unused files in the write part. This old files can be 
compacted to and moved to the 'unused' part to give a continuous area to
use as write part. These files could even be moved to a slower media
(if available).

Log files will remain in 'write/unused' sections until searched.

Comments?

/RogerL

             reply	other threads:[~2006-07-10  7:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  7:04 Roger Larsson [this message]
2006-07-10  8:27 ` [RFC] Copy on First Read? Andreas Dilger
2006-07-10 10:25   ` Roger Larsson
2006-07-10 17:59     ` Theodore Tso
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=200607100904.44983.roger.larsson@norran.net \
    --to=roger.larsson@norran.net \
    --cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox