From: Allison Henderson <achender@linux.vnet.ibm.com>
To: linux-ext4@vger.kernel.org, xiaoqiangnk@gmail.com
Cc: Allison Henderson <achender@linux.vnet.ibm.com>
Subject: [PATCH 0/6] Rename delayed extents to status extents
Date: Fri, 9 Mar 2012 21:41:19 -0700 [thread overview]
Message-ID: <1331354485-18515-1-git-send-email-achender@linux.vnet.ibm.com> (raw)
This set is based on Yongqiang's
"[PATCH V3 0/6] ext4: add delayed extent tree for ext4".
This patch set renames the changes introduced by the delayed
extent set to follow a "status extent" naming scheme. This
set does not yet introduce any functional changes other than renaming.
The purpose of the rename it to prepare the set for supporting
allocated extents as well as delayed extents. Then once we have
it tracking allocated extents, we can implement extent locks.
Merging the solutions will eliminate the need to maintain yet
another tree, sense both solutions are an rbtree of extents.
Sense delayed extents have not yet been merged, the plan is
to merge this set with the existing delayed extent set, and
the new "status extent" set will be the foundation for extent
locks.
Yongqiang, if this all looks good to you, I will merge
our sets and include it as part of the extent lock set,
once I get the rest of it finished up. Thx!
Allison Henderson (6):
Rename de patch1 from de to se scheme
Rename de patch2 from de to se scheme
Rename de patch3 from de to se scheme
Rename de patch4 from de to se scheme
Rename de patch5 from de to se scheme
Rename de patch6 from de to se scheme
fs/ext4/Makefile | 2 +-
fs/ext4/delayed_extents.c | 415 --------------------------------------------
fs/ext4/delayed_extents.h | 40 -----
fs/ext4/ext4.h | 4 +-
fs/ext4/extents.c | 24 ++--
fs/ext4/indirect.c | 2 +-
fs/ext4/inode.c | 4 +-
fs/ext4/status_extents.c | 417 +++++++++++++++++++++++++++++++++++++++++++++
fs/ext4/status_extents.h | 40 +++++
fs/ext4/super.c | 8 +-
10 files changed, 479 insertions(+), 477 deletions(-)
delete mode 100644 fs/ext4/delayed_extents.c
delete mode 100644 fs/ext4/delayed_extents.h
create mode 100644 fs/ext4/status_extents.c
create mode 100644 fs/ext4/status_extents.h
next reply other threads:[~2012-03-10 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 4:41 Allison Henderson [this message]
2012-03-10 4:41 ` [PATCH 1/6] Rename de patch1 from de to se scheme Allison Henderson
2012-03-10 4:41 ` [PATCH 2/6] Rename de patch2 " Allison Henderson
2012-03-10 4:41 ` [PATCH 3/6] Rename de patch3 " Allison Henderson
2012-03-10 4:41 ` [PATCH 4/6] Rename de patch4 " Allison Henderson
2012-03-10 4:41 ` [PATCH 5/6] Rename de patch5 " Allison Henderson
2012-03-10 4:41 ` [PATCH 6/6] Rename de patch6 " Allison Henderson
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=1331354485-18515-1-git-send-email-achender@linux.vnet.ibm.com \
--to=achender@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xiaoqiangnk@gmail.com \
/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).