From: Dave Hansen <haveblue@us.ibm.com>
To: Timothy Miller <miller@techsource.com>
Cc: root@chaos.analogic.com, Alok Mooley <rangdi@yahoo.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: Active Memory Defragmentation: Our implementation & problems
Date: 04 Feb 2004 11:43:53 -0800 [thread overview]
Message-ID: <1075923832.27944.391.camel@nighthawk> (raw)
In-Reply-To: <40214A11.3060007@techsource.com>
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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-02-04 19:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 4:46 Alok Mooley
2004-02-03 21:26 ` Dave Hansen
2004-02-03 22:26 ` Martin J. Bligh
2004-02-04 5:09 ` Alok Mooley
2004-02-04 5:24 ` Mike Fedyk
2004-02-04 5:54 ` Dave Hansen
2004-02-04 6:05 ` Martin J. Bligh
2004-02-04 6:22 ` Dave Hansen
2004-02-04 6:29 ` Martin J. Bligh
2004-02-04 6:40 ` Dave Hansen
2004-02-04 7:17 ` Martin J. Bligh
2004-02-04 8:30 ` Andrew Morton
2004-02-04 6:53 ` Doubt about statm_pgd_range patch Arunkumar
2004-02-04 6:57 ` Active Memory Defragmentation: Our implementation & problems IWAMOTO Toshihiro
2004-02-04 7:10 ` Dave Hansen
2004-02-04 7:50 ` IWAMOTO Toshihiro
2004-02-04 10:33 ` Hirokazu Takahashi
2004-02-04 18:33 ` Alok Mooley
2004-02-04 18:46 ` Dave Hansen
2004-02-04 18:54 ` Alok Mooley
2004-02-04 19:07 ` Richard B. Johnson
2004-02-04 19:18 ` Alok Mooley
2004-02-04 19:33 ` Richard B. Johnson
2004-02-05 5:07 ` Alok Mooley
2004-02-05 19:03 ` Pavel Machek
2004-02-04 19:35 ` Dave McCracken
2004-02-04 21:59 ` Timothy Miller
2004-02-04 23:24 ` Dave Hansen
2004-02-05 16:32 ` Dave McCracken
2004-02-04 19:37 ` Timothy Miller
2004-02-04 19:43 ` Dave Hansen [this message]
2004-02-04 19:59 ` Richard B. Johnson
2004-02-04 19:56 ` Dave Hansen
2004-02-05 5:19 ` Alok Mooley
2004-02-04 20:12 Mark_H_Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1075923832.27944.391.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miller@techsource.com \
--cc=rangdi@yahoo.com \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox