From: Mark Gross <mgross@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@in.ibm.com>, Mel Gorman <mel@skynet.ie>,
npiggin@suse.de, clameter@engr.sgi.com, mingo@elte.hu,
jschopp@austin.ibm.com, arjan@infradead.org, mbligh@mbligh.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: The performance and behaviour of the anti-fragmentation related patches
Date: Fri, 2 Mar 2007 08:20:23 -0800 [thread overview]
Message-ID: <20070302162023.GA4691@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703012105080.3953@woody.linux-foundation.org>
On Thu, Mar 01, 2007 at 09:11:58PM -0800, Linus Torvalds wrote:
>
> On Thu, 1 Mar 2007, Andrew Morton wrote:
> >
> > On Thu, 1 Mar 2007 19:44:27 -0800 (PST) Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > > In other words, I really don't see a huge upside. I see *lots* of
> > > downsides, but upsides? Not so much. Almost everybody who wants unplug
> > > wants virtualization, and right now none of the "big virtualization"
> > > people would want to have kernel-level anti-fragmentation anyway sicne
> > > they'd need to do it on their own.
> >
> > Agree with all that, but you're missing the other application: power
> > saving. FBDIMMs take eight watts a pop.
>
> This is a hardware problem. Let's see how long it takes for Intel to
> realize that FBDIMM's were a hugely bad idea from a power perspective.
>
> Yes, the same issues exist for other DRAM forms too, but to a *much*
> smaller degree.
DDR3-1333 may be better than FBDIMM's but don't count on it being much
better.
>
> Also, IN PRACTICE you're never ever going to see this anyway. Almost
> everybody wants bank interleaving, because it's a huge performance win on
> many loads. That, in turn, means that your memory will be spread out over
> multiple DIMM's even for a single page, much less any bigger area.
4-way interleave across banks on systems may not be as common as you may
think for future chip sets. 2-way interleave across DIMMs within a bank
will stay.
Also the performance gains between 2 and 4 way interleave have been
shown to be hard to measure. It may be counter intuitive but its not
the huge performance win you may expect. At least in some of the test
cases I've seen reported showed it to be under the noise floor of the
lmbench test cases.
>
> In other words - forget about DRAM power savings. It's not realistic. And
> if you want low-power, don't use FBDIMM's. It really *is* that simple.
>
DDR3-1333 won't be much better.
> (And yes, maybe FBDIMM controllers in a few years won't use 8 W per
> buffer. I kind of doubt that, since FBDIMM fairly fundamentally is highish
> voltage swings at high frequencies.)
>
> Also, on a *truly* idle system, we'll see the power savings whatever we
> do, because the working set will fit in D$, and to get those DRAM power
> savings in reality you need to have the DRAM controller shut down on its
> own anyway (ie sw would only help a bit).
>
> The whole DRAM power story is a bedtime story for gullible children. Don't
> fall for it. It's not realistic. The hardware support for it DOES NOT
> EXIST today, and probably won't for several years. And the real fix is
> elsewhere anyway (ie people will have to do a FBDIMM-2 interface, which
> is against the whole point of FBDIMM in the first place, but that's what
> you get when you ignore power in the first version!).
>
Hardware support for some of this is coming this year in the ATCA space
on the MPCBL0050. The feature is a bit experimental, and
power/performance benefits will be workload and configuration
dependent. Its not a bed time story.
--mgross
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-03-02 16:20 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 10:12 The performance and behaviour of the anti-fragmentation related patches Mel Gorman
2007-03-02 0:09 ` Andrew Morton
2007-03-02 0:44 ` Linus Torvalds
2007-03-02 1:52 ` Balbir Singh
2007-03-02 3:44 ` Linus Torvalds
2007-03-02 3:59 ` Andrew Morton
2007-03-02 5:11 ` Linus Torvalds
2007-03-02 5:50 ` KAMEZAWA Hiroyuki
2007-03-02 6:15 ` Paul Mundt
2007-03-02 17:01 ` Mel Gorman
2007-03-02 16:20 ` Mark Gross [this message]
2007-03-02 17:07 ` Andrew Morton
2007-03-02 17:35 ` Mark Gross
2007-03-02 18:02 ` Andrew Morton
2007-03-02 19:02 ` Mark Gross
2007-03-02 17:16 ` Linus Torvalds
2007-03-02 18:45 ` Mark Gross
2007-03-02 19:03 ` Linus Torvalds
2007-03-02 23:58 ` Martin J. Bligh
2007-03-02 4:18 ` Balbir Singh
2007-03-02 5:13 ` Jeremy Fitzhardinge
2007-03-06 4:16 ` Paul Mackerras
2007-03-02 16:58 ` Mel Gorman
2007-03-02 17:05 ` Joel Schopp
2007-03-05 3:21 ` Nick Piggin
2007-03-05 15:20 ` Joel Schopp
2007-03-05 16:01 ` Nick Piggin
2007-03-05 16:45 ` Joel Schopp
2007-05-03 8:49 ` Andy Whitcroft
2007-03-02 1:39 ` Balbir Singh
2007-03-02 2:34 ` KAMEZAWA Hiroyuki
2007-03-02 3:05 ` Christoph Lameter
2007-03-02 3:57 ` Nick Piggin
2007-03-02 4:06 ` Christoph Lameter
2007-03-02 4:21 ` Nick Piggin
2007-03-02 4:31 ` Christoph Lameter
2007-03-02 5:06 ` Nick Piggin
2007-03-02 5:40 ` Christoph Lameter
2007-03-02 5:49 ` Nick Piggin
2007-03-02 5:53 ` Christoph Lameter
2007-03-02 6:08 ` Nick Piggin
2007-03-02 6:19 ` Christoph Lameter
2007-03-02 6:29 ` Nick Piggin
2007-03-02 6:51 ` Christoph Lameter
2007-03-02 7:03 ` Andrew Morton
2007-03-02 7:19 ` Nick Piggin
2007-03-02 7:44 ` Christoph Lameter
2007-03-02 8:12 ` Nick Piggin
2007-03-02 8:21 ` Christoph Lameter
2007-03-02 8:38 ` Nick Piggin
2007-03-02 17:09 ` Christoph Lameter
2007-03-04 1:26 ` Rik van Riel
2007-03-04 1:51 ` Andrew Morton
2007-03-04 1:58 ` Rik van Riel
2007-03-02 5:50 ` Christoph Lameter
2007-03-02 4:29 ` Andrew Morton
2007-03-02 4:33 ` Christoph Lameter
2007-03-02 4:58 ` Andrew Morton
2007-03-02 4:20 ` Paul Mundt
2007-03-02 13:50 ` Arjan van de Ven
2007-03-02 15:29 ` Rik van Riel
2007-03-02 16:58 ` Andrew Morton
2007-03-02 17:09 ` Mel Gorman
2007-03-02 17:23 ` Christoph Lameter
2007-03-02 17:35 ` Andrew Morton
2007-03-02 17:43 ` Rik van Riel
2007-03-02 18:06 ` Andrew Morton
2007-03-02 18:15 ` Christoph Lameter
2007-03-02 18:23 ` Andrew Morton
2007-03-02 18:23 ` Rik van Riel
2007-03-02 19:31 ` Christoph Lameter
2007-03-02 19:40 ` Rik van Riel
2007-03-02 21:12 ` Bill Irwin
2007-03-02 21:19 ` Rik van Riel
2007-03-02 21:52 ` Andrew Morton
2007-03-02 22:03 ` Rik van Riel
2007-03-02 22:22 ` Andrew Morton
2007-03-02 22:34 ` Rik van Riel
2007-03-02 22:51 ` Martin Bligh
2007-03-02 22:54 ` Rik van Riel
2007-03-02 23:28 ` Martin J. Bligh
2007-03-03 0:24 ` Andrew Morton
2007-03-02 22:52 ` Chuck Ebbert
2007-03-02 22:59 ` Andrew Morton
2007-03-02 23:20 ` Rik van Riel
2007-03-03 1:40 ` William Lee Irwin III
2007-03-03 1:58 ` Andrew Morton
2007-03-03 3:55 ` William Lee Irwin III
2007-03-03 0:33 ` William Lee Irwin III
2007-03-03 0:54 ` Andrew Morton
2007-03-03 3:15 ` Christoph Lameter
2007-03-03 4:19 ` William Lee Irwin III
2007-03-03 17:16 ` Martin J. Bligh
2007-03-03 17:50 ` Christoph Lameter
2007-03-02 20:59 ` Bill Irwin
2007-03-02 1:52 ` Bill Irwin
2007-03-02 10:38 ` Mel Gorman
2007-03-02 16:31 ` Joel Schopp
2007-03-02 21:37 ` Bill Irwin
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=20070302162023.GA4691@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=balbir@in.ibm.com \
--cc=clameter@engr.sgi.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=mel@skynet.ie \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).