On Wed, 2004-02-04 at 11:37, Timothy Miller wrote: > Would memory fragmentation have any appreciable impact on L2 cache line > collisions? > Would defragmenting it help? Nope. The L2 lines are 32 or 64 bytes long, and the only unit we can defrag in is pages which are 4k. Since everything is aligned, a cacheline cannot cross a page. > In the case of the Opteron, there is a 1M cache that is (I forget) N-way > set associative, and it's physically indexed. If a bunch of pages were > located such that there were a disproportionately large number of lines > which hit the same tag, you could be thrashing the cache. > > There are two ways to deal with this: (1) intelligently locates pages > in physical memory; (2) hope that natural entropy keeps things random > enough that it doesn't matter. You're talking about page coloring now. That a whole different debate. I think it's been discussed here before. :) It's good. It's bad. It's good. It's bad. --dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: Active Memory Defragmentation: Our implementation & problemsAlok Mooley
- Re: Active Memory Defragmentation: Our implementation & problemsRichard B. Johnson
- Re: Active Memory Defragmentation: Our implementation & problemsTimothy Miller
- Prev by Date: Re: Active Memory Defragmentation: Our implementation & problems
- Next by Date: Re: Kernel 2.x POSIX Compliance/Conformance...
- Previous by thread: Re: Active Memory Defragmentation: Our implementation & problems
- Next by thread: Re: Active Memory Defragmentation: Our implementation & problems
- Indexes:[Main][Thread]