From: Nikolay Borisov <nborisov@suse.com>
To: bo.li.liu@oracle.com, dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Remove pair of bio_get/put in btrfs_schedule_bio
Date: Wed, 13 Dec 2017 09:18:12 +0200 [thread overview]
Message-ID: <f57db38f-02e0-9f10-d040-b2c60320439c@suse.com> (raw)
In-Reply-To: <20171212220944.GA19371@lim.localdomain>
On 13.12.2017 00:09, Liu Bo wrote:
> On Tue, Dec 12, 2017 at 07:52:38PM +0100, David Sterba wrote:
>> On Mon, Dec 11, 2017 at 02:57:56PM -0800, Liu Bo wrote:
>>> On Mon, Dec 11, 2017 at 04:38:48PM +0200, Nikolay Borisov wrote:
>>>> This code was added in 492bb6deee34 ("Btrfs: Hold a reference on bios
>>>> during submit_bio, add some extra bio checks"). However, holding a
>>>> reference on a bio is necessary only if it's going to be referenced
>>>> after the submit_bio returns and the bio is completed. In this
>>>> particular instance this is not the case so there is no need to hold
>>>> an extra reference since we directly return.
>>>>
>>>
>>> Looks good. If possible, please also drop other unnecessary bio_get()
>>> in btrfs.
>>
>> You mean everywhere with similar context like in this patch?
>>
>
> Right, there're several places where bio_get() is put before running
> functions but bio_put() is also put immediately without referencing
> bio.
I've already created patches for those and put them through fstests.
Will send them later
>
> thanks,
> -liubo
>
prev parent reply other threads:[~2017-12-13 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 14:38 [PATCH] btrfs: Remove pair of bio_get/put in btrfs_schedule_bio Nikolay Borisov
2017-12-11 22:57 ` Liu Bo
2017-12-12 18:52 ` David Sterba
2017-12-12 22:09 ` Liu Bo
2017-12-13 7:18 ` Nikolay Borisov [this message]
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=f57db38f-02e0-9f10-d040-b2c60320439c@suse.com \
--to=nborisov@suse.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--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