hat.com; sta...@vger.kernel.org
> Subject: RE: [PATCH 3/5] Drivers: hv: vmbus: Fix a bug in
> hv_need_to_signal_on_read()
>
>
>
> > -Original Message-
> > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> > Sent: Tuesday, March 22, 2016 2:56 AM
>
nical.com;
> jasow...@redhat.com; sta...@vger.kernel.org
> Subject: Re: [PATCH 3/5] Drivers: hv: vmbus: Fix a bug in
> hv_need_to_signal_on_read()
>
> KY Srinivasan writes:
>
> >> -Original Message-
> >> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> >&
driverproject.org; o...@aepfle.de; a...@canonical.com;
>> jasow...@redhat.com; sta...@vger.kernel.org
>> Subject: Re: [PATCH 3/5] Drivers: hv: vmbus: Fix a bug in
>> hv_need_to_signal_on_read()
>>
>> "K. Y. Srinivasan" writes:
>>
>> > We need to issue a
; jasow...@redhat.com; sta...@vger.kernel.org
> Subject: Re: [PATCH 3/5] Drivers: hv: vmbus: Fix a bug in
> hv_need_to_signal_on_read()
>
> "K. Y. Srinivasan" writes:
>
> > We need to issue a full memory barrier prior making a signalling
> > decision.
>
"K. Y. Srinivasan" writes:
> We need to issue a full memory barrier prior making a signalling
> decision.
Any reason this should be mb()? This is pretty strong and will probably
lead to performace regression ... and, btw, we have another mb() in
hv_ringbuffer_read().
Could you please describe t
