From: Christoph Lameter <cl@linux.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
lsf@lists.linux-foundation.org, Linux-MM <linux-mm@kvack.org>,
Wu Fengguang <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Lsf] [LSF/MM TOPIC] Testing Large-Memory Hardware
Date: Tue, 18 Mar 2014 12:26:40 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1403181224000.23935@nuc> (raw)
In-Reply-To: <20140318165059.GI22095@laptop.programming.kicks-ass.net>
On Tue, 18 Mar 2014, Peter Zijlstra wrote:
> > My gut reaction was that we'd probably be better served by putting
> > resources in to systems with higher core counts rather than lots of RAM.
> > I have encountered the occasional boot bug on my 1TB system, but it's
> > far from a frequent occurrence, and even more infrequent to encounter
> > things at runtime.
> >
> > Would folks agree with that? What kinds of tests, benchmarks, stress
> > tests, etc... do folks run that are both valuable and can only be run on
> > a system with a large amount of actual RAM?
>
> We had a sched-numa + kvm fail on really large systems the other day,
> but yeah in general such problems tend to be rare. Then again, without
> test coverage they will always be rare, for even if there were problems,
> nobody would notice :-)
SGI had systems out there up to few PB of RAM. There were a couple of
tricks to get this going. Bootup time was pretty long. I/O has to be done
carefully. The MM subsystem used to work with these sizes (I have not had
a chance to verify that recently).
This was Itanium with 64K page size so you had a factor of 16 less page
structs to process. What I saw there is one of the reasons why I would
like to see larger page support in the kernel. Managing massive amounts of
4k pages is creation far too much overhead.
--
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>
prev parent reply other threads:[~2014-03-18 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 16:32 Dave Hansen
2014-03-18 16:50 ` [Lsf] " Peter Zijlstra
2014-03-18 17:26 ` Christoph Lameter [this message]
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=alpine.DEB.2.10.1403181224000.23935@nuc \
--to=cl@linux.com \
--cc=dave.hansen@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf@lists.linux-foundation.org \
--cc=peterz@infradead.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