From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 00/12] Misc cleanups
Date: Wed, 9 Nov 2016 18:04:15 +0100 [thread overview]
Message-ID: <cover.1478710770.git.dsterba@suse.com> (raw)
Hi,
here's a bunch of cleanups and potential speed improvements when copying extent
buffer pages, there are some special cases. I haven't done any performance
measurements though.
Patchset target is 4.10, can be found in branch misc-cleanups-4.10 in my repos.
----------------------------------------------------------------
David Sterba (12):
btrfs: reada, cleanup remove unneeded variable in __readahead_hook
btrfs: reada, remove unused parameter from __readahead_hook
btrfs: reada, sink start parameter to btree_readahead_hook
btrfs: reada, remove pointless BUG_ON in reada_find_extent
btrfs: reada, remove pointless BUG_ON check for fs_info
btrfs: remove trivial helper btrfs_find_tree_block
btrfs: delete unused member from superblock
btrfs: introduce helpers for updating eb uuids
btrfs: use new helpers to set uuids in eb
btrfs: use specialized page copying helpers in btrfs_clone_extent_buffer
btrfs: remove constant parameter to memset_extent_buffer and rename it
btrfs: add optimized version of eb to eb copy
fs/btrfs/ctree.c | 49 ++++++++++++++++------------------------
fs/btrfs/ctree.h | 3 +--
fs/btrfs/disk-io.c | 26 +++++++--------------
fs/btrfs/disk-io.h | 2 --
fs/btrfs/extent-tree.c | 4 ++--
fs/btrfs/extent_io.c | 47 +++++++++++++++++++++++++++++++++-----
fs/btrfs/extent_io.h | 9 ++++++--
fs/btrfs/file-item.c | 2 +-
fs/btrfs/free-space-cache.c | 4 ++--
fs/btrfs/inode.c | 2 +-
fs/btrfs/ioctl.c | 10 ++++----
fs/btrfs/reada.c | 24 ++++++--------------
fs/btrfs/relocation.c | 2 +-
fs/btrfs/tests/extent-io-tests.c | 2 +-
fs/btrfs/volumes.c | 6 ++---
15 files changed, 98 insertions(+), 94 deletions(-)
next reply other threads:[~2016-11-09 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 17:04 David Sterba [this message]
2016-11-09 17:04 ` [PATCH 01/12] btrfs: reada, cleanup remove unneeded variable in __readahead_hook David Sterba
2016-11-09 17:04 ` [PATCH 02/12] btrfs: reada, remove unused parameter from __readahead_hook David Sterba
2016-11-09 17:04 ` [PATCH 03/12] btrfs: reada, sink start parameter to btree_readahead_hook David Sterba
2016-11-09 17:04 ` [PATCH 04/12] btrfs: reada, remove pointless BUG_ON in reada_find_extent David Sterba
2016-11-09 17:04 ` [PATCH 05/12] btrfs: reada, remove pointless BUG_ON check for fs_info David Sterba
2016-11-09 17:04 ` [PATCH 06/12] btrfs: remove trivial helper btrfs_find_tree_block David Sterba
2016-11-09 17:04 ` [PATCH 07/12] btrfs: delete unused member from superblock David Sterba
2016-11-09 17:04 ` [PATCH 08/12] btrfs: introduce helpers for updating eb uuids David Sterba
2016-11-09 17:04 ` [PATCH 09/12] btrfs: use new helpers to set uuids in eb David Sterba
2016-11-09 17:04 ` [PATCH 10/12] btrfs: use specialized page copying helpers in btrfs_clone_extent_buffer David Sterba
2016-11-09 17:04 ` [PATCH 11/12] btrfs: remove constant parameter to memset_extent_buffer and rename it David Sterba
2016-11-09 17:04 ` [PATCH 12/12] btrfs: add optimized version of eb to eb copy David Sterba
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 18:36 [PATCH 00/12] Misc cleanups marcandre.lureau
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.1478710770.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.