From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/3] 3 misc patches
Date: Thu, 21 Nov 2019 14:03:28 +0200 [thread overview]
Message-ID: <20191121120331.29070-1-nborisov@suse.com> (raw)
Here are 3 misc patches. First one is an optimsation to prevent issuing discards
for reserved but not written extents. The other 2 simply get rid of
__btrfs_free_reserved_extent by moving its relevant parts to the two wrappers.
Nikolay Borisov (3):
btrfs: Don't discard unwritten extents
btrfs: Open code __btrfs_free_reserved_extent in
btrfs_free_reserved_extent
btrfs: Rename __btrfs_free_reserved_extent to
btrfs_pin_reserved_extent
fs/btrfs/ctree.h | 4 ++--
fs/btrfs/extent-tree.c | 44 ++++++++++++++++++------------------------
fs/btrfs/inode.c | 7 ++++++-
fs/btrfs/tree-log.c | 12 +++++-------
4 files changed, 32 insertions(+), 35 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-21 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 12:03 Nikolay Borisov [this message]
2019-11-21 12:03 ` [PATCH 1/3] btrfs: Don't discard unwritten extents Nikolay Borisov
2019-11-27 16:06 ` David Sterba
2019-11-27 16:15 ` David Sterba
2019-11-27 16:23 ` Nikolay Borisov
2019-11-27 17:37 ` Filipe Manana
2019-11-21 12:03 ` [PATCH 2/3] btrfs: Open code __btrfs_free_reserved_extent in btrfs_free_reserved_extent Nikolay Borisov
2019-11-27 18:55 ` David Sterba
2019-11-29 8:44 ` Nikolay Borisov
2019-11-21 12:03 ` [PATCH 3/3] btrfs: Rename __btrfs_free_reserved_extent to btrfs_pin_reserved_extent Nikolay Borisov
2019-11-28 11:14 ` David Sterba
2019-12-03 17:16 ` [PATCH 0/3] 3 misc patches 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=20191121120331.29070-1-nborisov@suse.com \
--to=nborisov@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).