linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/6] ext4: status extents
Date: Wed, 18 Apr 2012 18:56:46 -0700	[thread overview]
Message-ID: <20120419015646.GW15164@tux1.beaverton.ibm.com> (raw)
In-Reply-To: <1334732838-25102-1-git-send-email-achender@linux.vnet.ibm.com>

On Wed, Apr 18, 2012 at 12:07:12AM -0700, Allison Henderson wrote:
> This set is based on the earlier delayed extent tree, but has
> been renamed to a "status extent" scheme.  The plan is that the
> tree will be expanded to track allocated extents and also
> support extent locks.  Thus status extents seemed like a
> more appropriate name.

How about "extent status tree" ?

> 
> Allison Henderson (6):
>   ext4: add two structures supporting status extent tree
>   ext4: add operations on status extent tree
>   ext4: initialize status extent tree
>   ext4: let ext4 maintian status extent trees

"maintain".

--D

>   ext4: reimplement fiemap on status extent tree
>   ext4: reimplement ext4_find_delay_alloc_range on status extent tree
> 
>  fs/ext4/Makefile         |    2 +-
>  fs/ext4/ext4.h           |    9 +-
>  fs/ext4/ext4_extents.h   |    3 +-
>  fs/ext4/extents.c        |  297 ++++-----------------------------
>  fs/ext4/indirect.c       |    3 +
>  fs/ext4/inode.c          |   83 ++++------
>  fs/ext4/status_extents.c |  417 ++++++++++++++++++++++++++++++++++++++++++++++
>  fs/ext4/status_extents.h |   40 +++++
>  fs/ext4/super.c          |   13 ++-
>  9 files changed, 545 insertions(+), 322 deletions(-)
>  create mode 100644 fs/ext4/status_extents.c
>  create mode 100644 fs/ext4/status_extents.h
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      parent reply	other threads:[~2012-04-19  1:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  7:07 [PATCH 0/6] ext4: status extents Allison Henderson
2012-04-18  7:07 ` [PATCH 1/6] ext4: add two structures supporting status extent tree Allison Henderson
2012-04-18  7:07 ` [PATCH 2/6] ext4: add operations on " Allison Henderson
2012-04-18  7:07 ` [PATCH 3/6] ext4: initialize " Allison Henderson
2012-04-18  7:07 ` [PATCH 4/6] ext4: let ext4 maintian status extent trees Allison Henderson
2012-04-18  7:07 ` [PATCH 5/6] ext4: reimplement fiemap on status extent tree Allison Henderson
2012-04-18  7:07 ` [PATCH 6/6] ext4: reimplement ext4_find_delay_alloc_range " Allison Henderson
2012-04-19  1:56 ` Darrick J. Wong [this message]

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=20120419015646.GW15164@tux1.beaverton.ibm.com \
    --to=djwong@us.ibm.com \
    --cc=achender@linux.vnet.ibm.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).