linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC V3] ext4: limit block allocations for	indirect-block files to < 2^32
Date: Thu, 10 Sep 2009 16:42:53 -0500	[thread overview]
Message-ID: <4AA972DD.3090607@redhat.com> (raw)
In-Reply-To: <20090910213337.GC6705@mit.edu>

Theodore Tso wrote:
> On Thu, Sep 10, 2009 at 04:16:32PM -0500, Eric Sandeen wrote:
>> Ok, fine by me.  I can send an update.
>>
>> Any suggestions on the naming issues?  (what's the official name for a
>> "not-extent-based-file?")
> 
> What I normally use is "extent-mapped file" and "indirect block mapped
> file", or "non-extent-mapped file".

I'll see if that can fit in a macro name nicely :)

Thanks,
-Eric

> 						- Ted


  reply	other threads:[~2009-09-10 21:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 22:17 [PATCH, RFC] ext4: limit block allocations for indirect-block files to < 2^32 Eric Sandeen
2009-09-05  3:21 ` [PATCH, RFC V2] " Eric Sandeen
2009-09-05 16:45   ` Andreas Dilger
2009-09-05 18:16     ` Eric Sandeen
2009-09-10 16:02     ` [PATCH, RFC V3] " Eric Sandeen
2009-09-10 16:53       ` Theodore Tso
2009-09-10 16:56         ` Eric Sandeen
2009-09-10 21:10       ` Andreas Dilger
2009-09-10 21:16         ` Eric Sandeen
2009-09-10 21:33           ` Theodore Tso
2009-09-10 21:42             ` Eric Sandeen [this message]
2009-09-10 21:51           ` Andreas Dilger
2009-09-10 21:57             ` Eric Sandeen
2009-09-10 23:19               ` Theodore Tso
2009-09-11 14:15                 ` Eric Sandeen
2009-09-10 22:01             ` Andreas Dilger
2009-09-14 20:03       ` [PATCH, RFC V4] " Eric Sandeen
2009-09-16 18:54         ` Theodore Tso

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=4AA972DD.3090607@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --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).