From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/3] Extent buffer accessor macros cleanup
Date: Tue, 20 Aug 2019 18:58:41 +0200 [thread overview]
Message-ID: <cover.1566320094.git.dsterba@suse.com> (raw)
Remove some conditions from eb accessors, eg. when the token pointer is
known to be valid, or when the eb/token pair does not change inside the
functions.
David Sterba (3):
btrfs: define separate btrfs_set/get_XX helpers
btrfs: assume valid token for btrfs_set/get_token helpers
btrfs: tie extent buffer and it's token together
fs/btrfs/ctree.c | 27 +++++++--------
fs/btrfs/ctree.h | 19 ++++-------
fs/btrfs/inode.c | 2 +-
fs/btrfs/struct-funcs.c | 73 ++++++++++++++++++++++++++++++++++-------
fs/btrfs/tree-log.c | 7 ++--
5 files changed, 83 insertions(+), 45 deletions(-)
--
2.22.0
next reply other threads:[~2019-08-20 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 16:58 David Sterba [this message]
2019-08-20 16:58 ` [PATCH 1/3] btrfs: define separate btrfs_set/get_XX helpers David Sterba
2019-08-20 16:58 ` [PATCH 2/3] btrfs: assume valid token for btrfs_set/get_token helpers David Sterba
2019-08-20 16:58 ` [PATCH 3/3] btrfs: tie extent buffer and it's token together 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.1566320094.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).