From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/4] Cleanup of bio_get/set
Date: Wed, 13 Dec 2017 10:25:36 +0200 [thread overview]
Message-ID: <1513153540-10737-1-git-send-email-nborisov@suse.com> (raw)
Hello,
Here is a series which cleans the btrfs source code of all the redundant
bio_get/set calls. After it's applied there is only a single bio_get inovcation
left in __alloc_device for the flush_bio (and that is wrong since it
leaks the bio, but this will be fixed in a follow up fix).
Nikolay Borisov (4):
btrfs: Remove redundant bio_get/set calls in compressed read/write
paths
btrfs: Remove redundant bio_get/set from submit_dio_repair_bio
btrfs: Remove redundan bio_get/bio_set pair from submit_one_bio
btrfs: Remove redundant pair of bio_get/set in __btrfs_submit_dio_bio
fs/btrfs/compression.c | 12 ------------
fs/btrfs/extent_io.c | 2 --
fs/btrfs/inode.c | 10 ++--------
3 files changed, 2 insertions(+), 22 deletions(-)
--
2.7.4
next reply other threads:[~2017-12-13 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 8:25 Nikolay Borisov [this message]
2017-12-13 8:25 ` [PATCH 1/4] btrfs: Remove redundant bio_get/set calls in compressed read/write paths Nikolay Borisov
2017-12-13 8:25 ` [PATCH 2/4] btrfs: Remove redundant bio_get/set from submit_dio_repair_bio Nikolay Borisov
2017-12-13 8:25 ` [PATCH 3/4] btrfs: Remove redundan bio_get/bio_set pair from submit_one_bio Nikolay Borisov
2017-12-13 8:25 ` [PATCH 4/4] btrfs: Remove redundant pair of bio_get/set in __btrfs_submit_dio_bio Nikolay Borisov
2018-01-02 15:40 ` [PATCH 0/4] Cleanup of bio_get/set 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=1513153540-10737-1-git-send-email-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).