linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/4] Remove indirect iterators for inode references
Date: Wed,  8 Jun 2022 23:35:57 +0200	[thread overview]
Message-ID: <cover.1654723641.git.dsterba@suse.com> (raw)

There's support for a generic iterator over inode references that is for
example used to resolve inode number to all paths but there's only one
such iterator implementation so it's not necessary, unless somebody has
an idea for more such iterators. There is a similar pattern used for
extent iterator utilizing the indirection, but I think we can remove it
for the inode refs.

David Sterba (4):
  btrfs: call inode_to_path directly and drop indirection
  btrfs: simplify parameters of backref iterators
  btrfs: sink iterator parameter to btrfs_ioctl_logical_to_ino
  btrfs: remove unused typedefs get_extent_t and btrfs_work_func_t

 fs/btrfs/async-thread.h |  1 -
 fs/btrfs/backref.c      | 88 +++++++++++++++++++++++------------------
 fs/btrfs/backref.h      |  3 +-
 fs/btrfs/extent_io.h    |  4 --
 fs/btrfs/ioctl.c        | 22 +----------
 5 files changed, 51 insertions(+), 67 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-06-08 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 21:35 David Sterba [this message]
2022-06-08 21:36 ` [PATCH 1/4] btrfs: call inode_to_path directly and drop indirection David Sterba
2022-06-08 21:36 ` [PATCH 2/4] btrfs: simplify parameters of backref iterators David Sterba
2022-06-08 21:36 ` [PATCH 3/4] btrfs: sink iterator parameter to btrfs_ioctl_logical_to_ino David Sterba
2022-06-08 21:36 ` [PATCH 4/4] btrfs: remove unused typedefs get_extent_t and btrfs_work_func_t David Sterba
2022-06-17 15:06 ` [PATCH 0/4] Remove indirect iterators for inode references David Sterba

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=cover.1654723641.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@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).