All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: "Burnes, James" <james.burnes@gwl.com>
Cc: Stewart Smith <stewart@flamingspork.com>,
	Tom Vier <tmv@comcast.net>, Scott Young <youngs1@sunyit.edu>,
	reiserfs-list@namesys.com
Subject: Re: Resier Fragmentation Effects (was compression vs performance)
Date: Thu, 08 Apr 2004 22:53:08 -0700	[thread overview]
Message-ID: <40763A44.4040107@namesys.com> (raw)
In-Reply-To: <3DF9165145FACB4C96977FF650C1E9040C469DBF@its-mail1.its.corp.gwl.com>

Burnes, James wrote:

>I thought nearly all filesystems designed since Berkeley FFS were nearly
>immune to fragmentation problems.
>
>After reading the following analysis at Harvard, it seems that
>fragmentation is still a problem.
>
>http://www.eecs.harvard.edu/~keith/research/tr94.html
>
>  
>
Yeah, I wish I had read this in 94.  V3 suffers from the same problems 
as FFS does as described in the abstract (all that I read, sorry about 
that, I really am a bit busy, so unless someone suggests I should read 
more.... ) .  V4 cures it though.

-- 
Hans


  reply	other threads:[~2004-04-09  5:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 17:00 Resier Fragmentation Effects (was compression vs performance) Burnes, James
2004-04-09  5:53 ` Hans Reiser [this message]
2004-04-09 18:13   ` Chris Mason
2004-04-10  6:09     ` Hans Reiser
2004-04-10 20:02       ` Chris Mason
2004-04-11 15:40         ` Hans Reiser
  -- strict thread matches above, loose matches on Subject: below --
2004-04-08 17:07 Burnes, James
2004-04-08 17:24 ` Dieter Nützel

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=40763A44.4040107@namesys.com \
    --to=reiser@namesys.com \
    --cc=james.burnes@gwl.com \
    --cc=reiserfs-list@namesys.com \
    --cc=stewart@flamingspork.com \
    --cc=tmv@comcast.net \
    --cc=youngs1@sunyit.edu \
    /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.