From: Peter Zijlstra <peterz@infradead.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
lsf@lists.linux-foundation.org,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [Lsf] [LSF/MM TOPIC] Testing Large-Memory Hardware
Date: Tue, 18 Mar 2014 17:50:59 +0100 [thread overview]
Message-ID: <20140318165059.GI22095@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <5328753B.2050107@intel.com>
On Tue, Mar 18, 2014 at 09:32:59AM -0700, Dave Hansen wrote:
> I have a quick topic that could perhaps be addressed along with the
> testing topic that Dave Jones proposed. I won't be attending, but there
> will be a couple of other Intel folks there. This should be a fairly
> quick thing to address.
>
> Topic:
>
> Fengguang Wu who runs the wonderful LKP and 0day build tests was
> recently asking if I thought there was value in adding a large-memory
> system, say with 1TB of RAM. LKP is the system that generates these
> kinds of automated bug reports and performance tests:
>
> http://lkml.org/lkml/2014/3/9/201
>
> 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 :-)
--
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:[~2014-03-18 16:51 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 ` Peter Zijlstra [this message]
2014-03-18 17:26 ` [Lsf] " Christoph Lameter
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=20140318165059.GI22095@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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 \
/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