On 28 March 2017 at 19:21, yoann padioleau wrote:
> but I fail to understand the meaning of S and B.
Synchronisation Barrier
On 28 March 2017 at 19:21, yoann padioleau wrote:
> For example I see this code in bcm/taslock.c
>
> coherence();
> l->key = 0;
> coherence();
>
> bcm/taslock.c seems actually mostly a copy paste of port/taslock.c
> with an extra call to coherence before the assignment abo
Hi,
What is exactly the logic of the calls to coherence?
When do we need to call coherence in the kernel?
For example I see this code in bcm/taslock.c
coherence();
l->key = 0;
coherence();
bcm/taslock.c seems actually mostly a copy paste of port/taslock.c
with an extra ca
