qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: famz@redhat.com, qemu-block@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 09/18] throttle-groups: protect throttled requests with a CoMutex
Date: Thu, 18 May 2017 14:08:32 +0200	[thread overview]
Message-ID: <cf5d85d7-26cc-2457-06fc-ca827ca1eaff@redhat.com> (raw)
In-Reply-To: <w51efvmgyj6.fsf@maestria.local.igalia.com>



On 18/05/2017 14:06, Alberto Garcia wrote:
> On Thu 11 May 2017 04:41:59 PM CEST, Paolo Bonzini wrote:
> 
>> --- a/include/sysemu/block-backend.h
>> +++ b/include/sysemu/block-backend.h
>> @@ -72,11 +72,8 @@ typedef struct BlockDevOps {
>>   * fields that must be public. This is in particular for QLIST_ENTRY() and
>>   * friends so that BlockBackends can be kept in lists outside block-backend.c */
>>  typedef struct BlockBackendPublic {
>> -    /* I/O throttling has its own locking, but also some fields are
>> -     * protected by the AioContext lock.
>> -     */
>> -
>> -    /* Protected by AioContext lock.  */
>> +    /* throttled_reqs_lock protects the CoQueues for throttled requests.  */
>> +    CoMutex      throttled_reqs_lock;
>>      CoQueue      throttled_reqs[2];
>>  
>>      /* Nonzero if the I/O limits are currently being ignored; generally
>>       * it is zero.  */
>>      unsigned int io_limits_disabled;
> 
> Does io_limits_disabled need locking too?

It uses atomic access since patch 3.

Paolo

  reply	other threads:[~2017-05-18 12:08 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 14:41 [Qemu-devel] [PATCH v2 00/18] Block layer thread safety, part 1 Paolo Bonzini
2017-05-11 14:41 ` [Qemu-devel] [PATCH 01/18] block: access copy_on_read with atomic ops Paolo Bonzini
2017-05-16 13:34   ` Stefan Hajnoczi
2017-05-11 14:41 ` [Qemu-devel] [PATCH 02/18] block: access quiesce_counter " Paolo Bonzini
2017-05-12  7:56   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-11 14:41 ` [Qemu-devel] [PATCH 03/18] block: access io_limits_disabled " Paolo Bonzini
2017-05-18 12:25   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-11 14:41 ` [Qemu-devel] [PATCH 04/18] block: access serialising_in_flight " Paolo Bonzini
2017-05-11 14:41 ` [Qemu-devel] [PATCH 05/18] block: access wakeup " Paolo Bonzini
2017-05-16 13:48   ` Stefan Hajnoczi
2017-05-11 14:41 ` [Qemu-devel] [PATCH 06/18] block: access io_plugged " Paolo Bonzini
2017-05-11 16:10   ` Eric Blake
2017-05-11 14:41 ` [Qemu-devel] [PATCH 07/18] throttle-groups: only start one coroutine from drained_begin Paolo Bonzini
2017-05-16 13:54   ` Stefan Hajnoczi
2017-05-17 21:50   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-11 14:41 ` [Qemu-devel] [PATCH 08/18] throttle-groups: do not use qemu_co_enter_next Paolo Bonzini
2017-05-16 14:44   ` Stefan Hajnoczi
2017-05-18 11:56   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-11 14:41 ` [Qemu-devel] [PATCH 09/18] throttle-groups: protect throttled requests with a CoMutex Paolo Bonzini
2017-05-16 14:47   ` Stefan Hajnoczi
2017-05-18 12:06   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-18 12:08     ` Paolo Bonzini [this message]
2017-05-18 12:19       ` Alberto Garcia
2017-05-11 14:42 ` [Qemu-devel] [PATCH 10/18] util: add stats64 module Paolo Bonzini
2017-05-16 14:47   ` Stefan Hajnoczi
2017-05-11 14:42 ` [Qemu-devel] [PATCH 11/18] block: use Stat64 for wr_highest_offset Paolo Bonzini
2017-05-11 14:42 ` [Qemu-devel] [PATCH 12/18] block: access write_gen with atomics Paolo Bonzini
2017-05-11 14:42 ` [Qemu-devel] [PATCH 13/18] block: protect tracked_requests and flush_queue with reqs_lock Paolo Bonzini
2017-05-16 14:50   ` Stefan Hajnoczi
2017-05-11 14:42 ` [Qemu-devel] [PATCH 14/18] block: introduce dirty_bitmap_mutex Paolo Bonzini
2017-05-16 14:55   ` Stefan Hajnoczi
2017-05-11 14:42 ` [Qemu-devel] [PATCH 15/18] migration/block: reset dirty bitmap before reading Paolo Bonzini
2017-05-16 15:03   ` Stefan Hajnoczi
2017-05-11 14:42 ` [Qemu-devel] [PATCH 16/18] block: protect modification of dirty bitmaps with a mutex Paolo Bonzini
2017-05-16 15:05   ` Stefan Hajnoczi
2017-05-11 14:42 ` [Qemu-devel] [PATCH 17/18] block: introduce block_account_one_io Paolo Bonzini
2017-05-16 15:07   ` Stefan Hajnoczi
2017-05-18 12:09   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-25  7:28   ` [Qemu-devel] " Fam Zheng
2017-05-11 14:42 ` [Qemu-devel] [PATCH 18/18] block: make accounting thread-safe Paolo Bonzini
2017-05-16 15:08   ` Stefan Hajnoczi
2017-05-18 12:16   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-05-11 18:21 ` [Qemu-devel] [PATCH v2 00/18] Block layer thread safety, part 1 no-reply
2017-05-11 19:24 ` no-reply
2017-05-16 15:08 ` Stefan Hajnoczi
2017-05-24  8:32 ` Paolo Bonzini
2017-05-25  7:40   ` Fam Zheng
2017-05-25  9:14     ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2017-05-25 16:17     ` [Qemu-devel] " Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2017-05-25 16:32 [Qemu-devel] [PATCH v3 " Paolo Bonzini
2017-05-25 16:32 ` [Qemu-devel] [PATCH 09/18] throttle-groups: protect throttled requests with a CoMutex Paolo Bonzini
2017-05-29 14:24   ` [Qemu-devel] [Qemu-block] " Alberto Garcia

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=cf5d85d7-26cc-2457-06fc-ca827ca1eaff@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berto@igalia.com \
    --cc=famz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).