On Mon, May 07, 2007 at 10:30:16AM -0700, Christoph Lameter wrote:
> Call this area "cpu shared" or so?
There are some fields in percpu section which are accessed by other
cpu's but not cache line aligned, e.g. cpu_idle_state, flush_state in
x86-64. We don't want to place those fields into same su
On Mon, May 07, 2007 at 10:30:16AM -0700, Christoph Lameter wrote:
> Call this area "cpu shared" or so?
Sure. cacheline_algined_in_smp was sort of indicating this. But this
name is short and also will clear the confusion.
But this still need to tap into per cpu infrastructure, so that the
new are
On Mon, 7 May 2007, Siddha, Suresh B wrote:
> > Ummm... The per cpu area is for exclusive use of a particular processor.
> > If there is contention in the per cpu area then a data object needs to be
> > removed from the per cpu area because the object is *not* accessed only
> > from a certain cpu.
On Sat, May 05, 2007 at 09:52:27AM -0700, Christoph Lameter wrote:
> On Fri, 4 May 2007, Fenghua Yu wrote:
>
> > This is follow-up for Suresh's runqueue align in smp patch at:
> > [1]http://www.uwsg.iu.edu/hypermail/linux/kernel/0704.1/0340.html
> >
> > The patches place all of smp cacheline aligne
On Fri, 4 May 2007, Fenghua Yu wrote:
> This is follow-up for Suresh's runqueue align in smp patch at:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0704.1/0340.html
>
> The patches place all of smp cacheline aligned percpu data into
> .data.percpu.cacheline_aligned_in_smp. Other percpu data i
This is follow-up for Suresh's runqueue align in smp patch at:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0704.1/0340.html
The patches place all of smp cacheline aligned percpu data into
.data.percpu.cacheline_aligned_in_smp. Other percpu data is still in
data.percpu section. The patches ca
6 matches
Mail list logo
