Eric wrote:
> But the initial pointer *should* be in a cache line shared by all cpus to get
> best performance.
No - not if that pointer is seldom used. Then its location does not
directly affect performance at all, and better for it to be used as
"inert filler" to fill out cache lines of words that are write hot.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Eric Dumazet <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Eric Dumazet <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Eric Dumazet <[email protected]>
- [PATCH] Cpuset: rcu optimization of page alloc hook
- Prev by Date: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
- Next by Date: 2.6.15-rc5 makes tons of: <NULL>: hw csum failure
- Previous by thread: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- Next by thread: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- Index(es):
 |