From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: Active Memory Defragmentation: Our implementation & problems From: Dave Hansen In-Reply-To: <40214A11.3060007@techsource.com> References: <20040204185446.91810.qmail@web9705.mail.yahoo.com> <40214A11.3060007@techsource.com> Content-Type: text/plain Message-Id: <1075923832.27944.391.camel@nighthawk> Mime-Version: 1.0 Date: 04 Feb 2004 11:43:53 -0800 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Timothy Miller Cc: root@chaos.analogic.com, Alok Mooley , linux-kernel , linux-mm List-ID: 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, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org