From: Kumar Gala <galak@kernel.crashing.org>
To: balbir@linux.vnet.ibm.com
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev@ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fake NUMA emulation for PowerPC
Date: Fri, 7 Dec 2007 15:55:20 -0600 [thread overview]
Message-ID: <975B5B2B-C1F3-4021-9AE2-8873FFE1BDEC@kernel.crashing.org> (raw)
In-Reply-To: <4759BCA2.1020809@linux.vnet.ibm.com>
On Dec 7, 2007, at 3:35 PM, Balbir Singh wrote:
> Olof Johansson wrote:
>> Hi,
>>
>> On Sat, Dec 08, 2007 at 02:44:25AM +0530, Balbir Singh wrote:
>>
>>> Comments are as always welcome!
>>
>> Care to explain what this is useful for? (Not saying it's a stupid
>> idea,
>> just wondering what the reason for doing it is).
>>
>
> In my case, I use it to test parts of my memory controller patches
> on an
> emulated NUMA machine. I plan to use it to test out page migration
> across nodes.
Can you explain that further. I'm still not clear on why this is
useful.
- k
next prev parent reply other threads:[~2007-12-07 21:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 21:14 Balbir Singh
2007-12-07 21:28 ` Olof Johansson
2007-12-07 21:35 ` Balbir Singh
2007-12-07 21:55 ` Kumar Gala [this message]
2007-12-07 22:12 ` Balbir Singh
2007-12-07 22:15 ` Kumar Gala
2007-12-07 22:18 ` Balbir Singh
2007-12-07 23:10 ` David Rientjes
2007-12-08 4:22 ` Balbir Singh
2007-12-09 13:16 ` Pavel Machek
2007-12-09 13:20 ` Balbir Singh
2007-12-07 23:06 ` David Rientjes
2007-12-07 21:30 ` Geert Uytterhoeven
2007-12-07 21:33 ` Dave Quigley
2007-12-07 21:35 ` Balbir Singh
2007-12-07 21:43 ` Balbir Singh
2007-12-07 21:58 ` Arnd Bergmann
2007-12-07 22:03 ` Balbir Singh
2007-12-07 22:01 ` Arnd Bergmann
2007-12-07 22:22 ` Balbir Singh
2007-12-07 22:11 ` Nathan Lynch
2007-12-07 22:26 ` Balbir Singh
2007-12-07 23:11 ` David Rientjes
2007-12-08 4:32 ` Balbir Singh
2007-12-08 4:45 ` David Rientjes
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=975B5B2B-C1F3-4021-9AE2-8873FFE1BDEC@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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
all inboxes | Powered by JetHome®