qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 6/7] block-copy: atomic .cancelled and .finished fields in


From: Paolo Bonzini
Subject: Re: [PATCH v2 6/7] block-copy: atomic .cancelled and .finished fields in BlockCopyCallState
Date: Fri, 21 May 2021 17:02:26 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1

On 20/05/21 17:34, Vladimir Sementsov-Ogievskiy wrote:

By adding acquire/release pairs, we ensure that .ret and .error_is_read
fields are written by block_copy_dirty_clusters before .finished is true.

As I already said, please, can we live with one mutex for now? finished, ret, error_is_read, all these variables are changing rarely. I doubt that performance is improved by these atomic operations. But complexity of the architecture increases exponentially.

The problem is that these are used outside coroutines. load-acquire/store-release is the simplest way to handle a "finished" flag really.

Paolo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]