From: yalin wang <yalin.wang2010@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] block: change to use atomic_inc_return_release()
Date: Tue, 17 Nov 2015 12:11:10 +0800 [thread overview]
Message-ID: <5C0352F2-3571-4EB4-87A2-4833D5BE8212@gmail.com> (raw)
In-Reply-To: <564AA13C.108@kernel.dk>
> On Nov 17, 2015, at 11:38, Jens Axboe <axboe@kernel.dk> wrote:
>
> On 11/16/2015 08:24 PM, yalin wang wrote:
>> Some arch define this atomic_inc_return_release() OP.
>
> That is a very vague commit message, you'll need a whole lot more than that... A commit message is supposed to describe the reason for the change. You provide no reason for the change.
>
>> diff --git a/block/bio.c b/block/bio.c
>> index fbc558b..b251857 100644
>> --- a/block/bio.c
>> +++ b/block/bio.c
>> @@ -310,8 +310,7 @@ static void bio_chain_endio(struct bio *bio, int error)
>> static inline void bio_inc_remaining(struct bio *bio)
>> {
>> bio->bi_flags |= (1 << BIO_CHAIN);
>> - smp_mb__before_atomic();
>> - atomic_inc(&bio->__bi_remaining);
>> + atomic_inc_return_release(&bio->__bi_remaining);
>
> Are these equivalent? Where's the documentation for this primitive? The previous code ensured that we ordered the dec of the remaining count with the update of the flags.
>
i just have a look at ARM64 implementation for this new atomic OP ,
but i don’t find doc in memory-barrier.txt . so i make this RFC for some response,
atomic_inc_return_release() should have store_release() class memory barriers .
in this example, smp_store_release() memory barrier is not enough ?
just make sure bi_flags update can been seen by other cores before update atomic counter.
atomic_inc_return_{release,acquire,relax} OP seems newly add to kernel .
But i don’t see much users in code .
Can it be used to replace lots of smp_mb__before_atomic() ?
Thanks
prev parent reply other threads:[~2015-11-17 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 3:24 yalin wang
2015-11-17 3:38 ` Jens Axboe
2015-11-17 4:11 ` yalin wang [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=5C0352F2-3571-4EB4-87A2-4833D5BE8212@gmail.com \
--to=yalin.wang2010@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®