From: Dave Hansen <dave@linux.vnet.ibm.com>
To: jlmales@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Commit 025cee7f8fef02af09b03c8e1cd9843cb32adf9b
Date: Thu, 28 Feb 2013 14:18:26 -0800 [thread overview]
Message-ID: <512FD7B2.40901@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130228171143.5c32726d.jlmales@gmail.com>
On 02/28/2013 02:11 PM, John L. Males wrote:
> Would the Linux Kernel under "unique" Virtual Memory Subsystem
> stress excite some of these "subtle bugs" in Linux Kernels
> prior to this change set for Commit
> 025cee7f8fef02af09b03c8e1cd9843cb32adf9b?
I don't think stress would really do it.
It also, as far as I know, only applies to 32-bit NUMA kernels where
CONFIG_NUMA was turned on _and_ where the machine actually was NUMA.
prev parent reply other threads:[~2013-02-28 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 22:11 Linux Kernel Commit 025cee7f8fef02af09b03c8e1cd9843cb32adf9b John L. Males
2013-02-28 22:18 ` Dave Hansen [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=512FD7B2.40901@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=jlmales@gmail.com \
--cc=linux-kernel@vger.kernel.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