From: Chrysostomos Nanakos <cnanakos@grnet.gr>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 2/2] block/archipelago: Use QEMU atomic builtins
Date: Mon, 01 Sep 2014 13:13:07 +0300 [thread overview]
Message-ID: <540446B3.8010907@grnet.gr> (raw)
In-Reply-To: <54043FC6.9090206@redhat.com>
On 09/01/2014 12:43 PM, Paolo Bonzini wrote:
> Il 01/09/2014 10:58, Chrysostomos Nanakos ha scritto:
>> Replace __sync builtins with the ones provided by QEMU
>> for atomic operations.
>>
>> Signed-off-by: Chrysostomos Nanakos <cnanakos@grnet.gr>
>> ---
>> block/archipelago.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/block/archipelago.c b/block/archipelago.c
>> index 34f72dc..fa8cd29 100644
>> --- a/block/archipelago.c
>> +++ b/block/archipelago.c
>> @@ -57,6 +57,7 @@
>> #include "qapi/qmp/qint.h"
>> #include "qapi/qmp/qstring.h"
>> #include "qapi/qmp/qjson.h"
>> +#include "qemu/atomic.h"
>>
>> #include <inttypes.h>
>> #include <xseg/xseg.h>
>> @@ -214,7 +215,7 @@ static void xseg_request_handler(void *state)
>>
>> xseg_put_request(s->xseg, req, s->srcport);
>>
>> - if ((__sync_add_and_fetch(&segreq->ref, -1)) == 0) {
>> + if ((atomic_add_fetch(&segreq->ref, -1)) == 0) {
> Why not just use "== 1" and avoid patch 1? :)
>
> (Also, you could use atomic_fetch_dec).
Nice catch!
>
>> if (!segreq->failed) {
>> reqdata->aio_cb->ret = segreq->count;
>> archipelago_finish_aiocb(reqdata);
>> @@ -233,7 +234,7 @@ static void xseg_request_handler(void *state)
>> segreq->count += req->serviced;
>> xseg_put_request(s->xseg, req, s->srcport);
>>
>> - if ((__sync_add_and_fetch(&segreq->ref, -1)) == 0) {
>> + if ((atomic_add_fetch(&segreq->ref, -1)) == 0) {
>> if (!segreq->failed) {
>> reqdata->aio_cb->ret = segreq->count;
>> archipelago_finish_aiocb(reqdata);
>> @@ -885,13 +886,13 @@ static int archipelago_aio_segmented_rw(BDRVArchipelagoState *s,
>> return 0;
>>
>> err_exit:
>> - __sync_add_and_fetch(&segreq->failed, 1);
>> + atomic_add_fetch(&segreq->failed, 1);
> You can use atomic_inc here.
Yes atomic_inc seems to be a lot better. Thanks!
>
> Paolo
>
>> if (segments_nr == 1) {
>> - if (__sync_add_and_fetch(&segreq->ref, -1) == 0) {
>> + if (atomic_add_fetch(&segreq->ref, -1) == 0) {
>> g_free(segreq);
>> }
>> } else {
>> - if ((__sync_add_and_fetch(&segreq->ref, -segments_nr + i)) == 0) {
>> + if ((atomic_add_fetch(&segreq->ref, -segments_nr + i)) == 0) {
What about this one? It seems easier to me to read the above and
understand what is going on.
By any means, it's up to you to accept patch 1 :)
Regards,
Chrysostomos.
>> g_free(segreq);
>> }
>> }
>>
next prev parent reply other threads:[~2014-09-01 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 8:58 [Qemu-devel] [PATCH v1 1/2] Extend header file for atomic operations Chrysostomos Nanakos
2014-09-01 8:58 ` [Qemu-devel] [PATCH v1 2/2] block/archipelago: Use QEMU atomic builtins Chrysostomos Nanakos
2014-09-01 9:43 ` Paolo Bonzini
2014-09-01 10:13 ` Chrysostomos Nanakos [this message]
2014-09-01 10:33 ` Paolo Bonzini
2014-09-01 10:39 ` Chrysostomos Nanakos
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=540446B3.8010907@grnet.gr \
--to=cnanakos@grnet.gr \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).