On 09/12/2015 11:59 AM, Ingo Molnar wrote:
>
> * Davidlohr Bueso wrote:
>
>> I think we should leave it as is.
>
> But ... given that these are shared-cached values (cached on all CPUs), this
> change would only be measurable in such a benchmark if the cache footprint of
> the
> test is
On 09/12/2015 11:59 AM, Ingo Molnar wrote:
>
> * Davidlohr Bueso wrote:
>
>> I think we should leave it as is.
>
> But ... given that these are shared-cached values (cached on all CPUs), this
> change would only be measurable in such a benchmark if the cache footprint of
>
* Davidlohr Bueso wrote:
> On Wed, 09 Sep 2015, Rasmus Villemoes wrote:
>
> >futex_hash() references two global variables: the base pointer
> >futex_queues and the size of the array futex_hashsize. The latter is
> >marked __read_mostly, while the former is not, so they are likely to
> >end up
* Davidlohr Bueso wrote:
> On Wed, 09 Sep 2015, Rasmus Villemoes wrote:
>
> >futex_hash() references two global variables: the base pointer
> >futex_queues and the size of the array futex_hashsize. The latter is
> >marked __read_mostly, while the former is not, so they are
On Wed, 09 Sep 2015, Rasmus Villemoes wrote:
futex_hash() references two global variables: the base pointer
futex_queues and the size of the array futex_hashsize. The latter is
marked __read_mostly, while the former is not, so they are likely to
end up very far from each other. This means that
On Wed, 09 Sep 2015, Rasmus Villemoes wrote:
futex_hash() references two global variables: the base pointer
futex_queues and the size of the array futex_hashsize. The latter is
marked __read_mostly, while the former is not, so they are likely to
end up very far from each other. This means that
futex_hash() references two global variables: the base pointer
futex_queues and the size of the array futex_hashsize. The latter is
marked __read_mostly, while the former is not, so they are likely to
end up very far from each other. This means that futex_hash() is
likely to encounter two cache
futex_hash() references two global variables: the base pointer
futex_queues and the size of the array futex_hashsize. The latter is
marked __read_mostly, while the former is not, so they are likely to
end up very far from each other. This means that futex_hash() is
likely to encounter two cache
8 matches
Mail list logo