On Tue, Sep 3, 2019 at 1:25 PM Peter Zijlstra <[email protected]> wrote:
>
> Why can't we frob this state into a line/word we already have to
> unconditionally touch, like the thread_info::flags word for example.
I agree, but we don't have any easily used flags left, I think.
But yes, it would be better to not have membarrier always dirty
another cacheline in the scheduler. So instead of
atomic_set(&t->membarrier_state,
atomic_read(&t->mm->membarrier_state));
it migth be better to do something like
if (mm->membarrier_state)
atomic_or(&t->membarrier_state, mm->membarrier_state);
or something along those lines - I think we've already brought in the
'mm' struct into the cache anyway, and we'd not do the write (and
dirty the destination cacheline) for the common case of no membarrier
usage.
But yes, it would be better still if we can re-use some already dirty
cache state.
I wonder if the easiest model might be to just use a percpu variable
instead for the membarrier stuff? It's not like it has to be in
'struct task_struct' at all, I think. We only care about the current
runqueues, and those are percpu anyway.
Linus
