From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/3] Simplify counting of extent buffer pages
Date: Tue, 24 Apr 2018 01:03:40 +0200 [thread overview]
Message-ID: <cover.1524523681.git.dsterba@suse.com> (raw)
Some low-hanging cleanup fruit. The argument bloat-o-meter shows some
improvements:
extent_io.c:cache_state_if_flags.part.27 -8 (8 -> 0)
extent_io.c:cache_state.part.28 -8 (8 -> 0)
extent_io.c:check_buffer_tree_ref.part.31 -24 (24 -> 0)
extent_io.c:mark_extent_buffer_accessed -8 (40 -> 32)
extent_io.c:alloc_extent_state_atomic.part.35 -8 (8 -> 0)
extent_io.c:flush_write_bio.isra.40 -16 (16 -> 0)
extent_io.c:set_page_extent_mapped.part.49 -8 (8 -> 0)
extent_io.c:extent_buffer_under_io.part.50 -8 (8 -> 0)
extent_io.c:__unlock_for_delalloc.isra.38 -8 (8 -> 0)
extent_io.c:merge_state.part.45 -48 (48 -> 0)
extent_io.c:repair_eb_io_failure -8 (72 -> 64)
extent_io.c:set_extent_buffer_dirty -8 (40 -> 32)
extent_io.c:__alloc_dummy_extent_buffer +8 (32 -> 40)
extent_io.c:write_one_eb +16 (152 -> 168)
David Sterba (3):
btrfs: simplify counting number of eb pages
btrfs: pass only eb to num_extent_pages
btrfs: switch types to int when counting eb pages
fs/btrfs/extent_io.c | 68 ++++++++++++++++++++++++++--------------------------
fs/btrfs/extent_io.h | 5 ++--
2 files changed, 36 insertions(+), 37 deletions(-)
--
2.16.2
next reply other threads:[~2018-04-23 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 23:03 David Sterba [this message]
2018-04-23 23:03 ` [PATCH 1/3] btrfs: simplify counting number of eb pages David Sterba
2018-04-24 5:59 ` Nikolay Borisov
2018-04-24 6:22 ` Qu Wenruo
2018-04-24 10:29 ` David Sterba
2018-04-24 10:36 ` Qu Wenruo
2018-04-23 23:03 ` [PATCH 2/3] btrfs: pass only eb to num_extent_pages David Sterba
2018-04-24 13:26 ` Nikolay Borisov
2018-04-23 23:03 ` [PATCH 3/3] btrfs: switch types to int when counting eb pages David Sterba
2018-04-24 13:26 ` Nikolay Borisov
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.1524523681.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.