Displaying 3 results from an estimated 3 matches for "store_releas".
Did you mean:
store_release
2019 Aug 08
3
[PATCH V4 7/9] vhost: do not use RCU to synchronize MMU notifier with worker
...the counter. Paired with smp_load_acquire()
in??????????????????????????????????????????????????????????????????????????????????????
???????? * vhost_vq_sync_access()
*/????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
??????? smp_store_release(&vq->counter,
--vq->counter);?????????????????????????????????????????????????????????????????????????????????????????????????
}???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
??????...
2019 Aug 07
2
[PATCH V4 7/9] vhost: do not use RCU to synchronize MMU notifier with worker
On Wed, Aug 07, 2019 at 03:06:15AM -0400, Jason Wang wrote:
> We used to use RCU to synchronize MMU notifier with worker. This leads
> calling synchronize_rcu() in invalidate_range_start(). But on a busy
> system, there would be many factors that may slow down the
> synchronize_rcu() which makes it unsuitable to be called in MMU
> notifier.
>
> So this patch switches use
2019 Aug 07
2
[PATCH V4 7/9] vhost: do not use RCU to synchronize MMU notifier with worker
On Wed, Aug 07, 2019 at 03:06:15AM -0400, Jason Wang wrote:
> We used to use RCU to synchronize MMU notifier with worker. This leads
> calling synchronize_rcu() in invalidate_range_start(). But on a busy
> system, there would be many factors that may slow down the
> synchronize_rcu() which makes it unsuitable to be called in MMU
> notifier.
>
> So this patch switches use