linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	Theodore Ts'o <tytso@mit.edu>,
	linux-ext4@vger.kernel.org
Subject: Re: Proposed design for big allocation blocks for ext4
Date: Fri, 25 Feb 2011 11:39:29 +0100	[thread overview]
Message-ID: <20110225103929.GD15464@bitwizard.nl> (raw)
In-Reply-To: <BBAF46A2-4F43-47E5-B98C-A33837EEF67E@dilger.ca>


On Fri, Feb 25, 2011 at 03:01:08AM -0700, Andreas Dilger wrote:

.... I was babbling.... 

> That is the time to load bitmaps in a non-flex_bg filesystem, which is
> the default for ext3-formatted filesystems.

OK! Already done!

Then I don't really understand what the problem is, so better ignore
me. :-)

	Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

  reply	other threads:[~2011-02-25 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  2:56 Proposed design for big allocation blocks for ext4 Theodore Ts'o
2011-02-25  8:21 ` Andreas Dilger
2011-02-25  9:15   ` Rogier Wolff
2011-02-25 10:01     ` Andreas Dilger
2011-02-25 10:39       ` Rogier Wolff [this message]
2011-02-25 12:57   ` Theodore Tso
2011-02-25 18:05     ` Amir Goldstein
2011-02-25 19:04       ` Ted Ts'o
2011-02-25 19:39         ` Andreas Dilger
2011-02-25 21:24         ` Amir Goldstein
2011-02-25 21:59 ` Joel Becker
2011-02-25 23:40   ` Ted Ts'o
2011-02-26  0:03     ` Joel Becker
2011-02-26  0:31       ` Ted Ts'o
2011-02-26  0:33         ` Joel Becker

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=20110225103929.GD15464@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).