From: Josh Triplett <josh@joshtriplett.org>
To: Kelley Nielsen <kelleynnn@gmail.com>
Cc: linux-btrfs@vger.kernel.org, opw-kernel@googlegroups.com
Subject: Re: [OPW kernel] [PATCH 0/3] bootstrapping btrfs_find_item_interface
Date: Sat, 2 Nov 2013 10:02:05 -0700 [thread overview]
Message-ID: <20131102170204.GK15704@leaf> (raw)
In-Reply-To: <cover.1383287959.git.kelleynnn@gmail.com>
On Thu, Oct 31, 2013 at 11:52:45PM -0700, Kelley Nielsen wrote:
> There are many btrfs functions that manually search the tree for an
> item. They all reimplement the same mechanism and differ in the
> conditions that they use to find the item. It has been proposed that a
> new core interface, btrfs_find_item, be created to take the place of
s/It has been proposed that ... be created/Zach Brown proposed creating .../
, judging by the Suggested-by in the patches.
> these functions, and standardize the search functionality.
>
> This patchset takes the first steps toward the implementation of this
> core interface. The first patch creates a starting point for the
> interface by moving one of the search functions, __inode_item, to
> ctree.c and renaming it with the core function name. The next two
> patches eliminate one similar helper function each by replacing their
> callers with calls to the new core function, and modifying the new core
> function to ensure it fulfills the purpose of the function being
> replaced.
>
> Kelley Nielsen (3):
> Bootstrap generic btrfs_find_item interface
> btrfs_find_item expanded to include find_root_ref funcionality
> btrfs_find_item expanded to include find_orphan_item functionality
>
> fs/btrfs/backref.c | 40 ++++----------------------------------
> fs/btrfs/ctree.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/btrfs/ctree.h | 2 ++
> fs/btrfs/disk-io.c | 3 ++-
> fs/btrfs/inode.c | 6 +++---
> fs/btrfs/orphan.c | 20 -------------------
> fs/btrfs/root-tree.c | 15 --------------
> fs/btrfs/tree-log.c | 3 ++-
> 8 files changed, 68 insertions(+), 76 deletions(-)
>
> --
> 1.8.1.2
>
> --
> You received this message because you are subscribed to the Google Groups "opw-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to opw-kernel+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
prev parent reply other threads:[~2013-11-02 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 6:52 [PATCH 0/3] bootstrapping btrfs_find_item_interface Kelley Nielsen
2013-11-01 6:53 ` [PATCH 1/3] Bootstrap generic btrfs_find_item interface Kelley Nielsen
2013-11-02 17:05 ` [OPW kernel] " Josh Triplett
2013-11-02 17:02 ` Josh Triplett [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=20131102170204.GK15704@leaf \
--to=josh@joshtriplett.org \
--cc=kelleynnn@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=opw-kernel@googlegroups.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).