public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [IDEA] - run-length compaction of block numbers
Date: Fri, 16 Jan 2004 14:36:03 -0600	[thread overview]
Message-ID: <40084B33.60209@comcast.net> (raw)
In-Reply-To: <200401161954.i0GJsEgj003906@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> 
> On the other hand, dynamic allocation of inodes is interesting, as it means
> you're not screwed if over time, the NBPI value for the filesystem changes (or
> if you simply guessed wrong at mkfs time) and you run out of inodes when you
> still have space free.  Reiserfs V3 already does this, in fact...
> 

As does JFS.  Anyone know about XFS?

-- 
========================================================================
Ian Pilcher                                        i.pilcher@comcast.net
========================================================================


  reply	other threads:[~2004-01-16 20:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 19:38 [IDEA] - run-length compaction of block numbers raymond jennings
2004-01-16 19:52 ` Randy.Dunlap
2004-01-16 19:54 ` Valdis.Kletnieks
2004-01-16 20:36   ` Ian Pilcher [this message]
2004-01-16 21:57     ` Mike Fedyk
2004-01-16 20:47   ` Hans Reiser
2004-01-16 22:38     ` Valdis.Kletnieks
2004-01-19 10:45       ` Hans Reiser
2004-01-19 16:20         ` Valdis.Kletnieks
2004-01-19 17:06           ` Hans Reiser
2004-02-08 11:38           ` Keith Owens
     [not found] <1eI8L-5fS-9@gated-at.bofh.it>
2004-01-16 20:01 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-01-29 16:40 raymond jennings

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=40084B33.60209@comcast.net \
    --to=i.pilcher@comcast.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox