Chris Wilson writes:
> Quoting Mika Kuoppala (2018-05-08 13:03:13)
>> Not all architectures guarantee that uncached read will
>> flush the write combining buffer. So marking it explicitly
>> is recommended [1].
>>
>> However we know the architecture we are operating on
>> and can avoid wmb as th
Not all architectures guarantee that uncached read will
flush the write combining buffer. So marking it explicitly
is recommended [1].
However we know the architecture we are operating on
and can avoid wmb as the UC store will flush the wcb [2].
Omit the wmb() before invalidate as redudant.
v2:
Quoting Mika Kuoppala (2018-05-08 13:03:13)
> Not all architectures guarantee that uncached read will
> flush the write combining buffer. So marking it explicitly
> is recommended [1].
>
> However we know the architecture we are operating on
> and can avoid wmb as the UC store will flush the wcb [
Not all architectures guarantee that uncached read will
flush the write combining buffer. So marking it explicitly
is recommended [1].
However we know the architecture we are operating on
and can avoid wmb as the UC store will flush the wcb [2].
Omit the wmb() before invalidate as redudant.
v2:
