Andi Kleen <[email protected]> writes:
>> So unless there is some other array that is sized by NR_IRQs
>> in the context switch path which could account for this in
>> other ways. It looks like you just got unlucky.
>
>
> TLB/cache profiling data might be useful?
> My bet would be more on cache effects.
The only way I can see that being true is if some irq was keeping
the cache line warm for something in the process startup.
I have trouble seeing how adding 1K to an already 1K data structure
can cause a cache fault that wasn't happening already.
>> The only hypothesis that I can seem to come up with is that maybe
>> you are getting an extra tlb now that you didn't use to.
>> I think the per cpu area is covered by huge pages but maybe not.
>
> It should be.
Which invalidates the tlb fault hypothesis unless it happens to lie
on the 2MB boundary.
Eric
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
