From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
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: Sat, 08 Dec 2007 03:48:45 +0530 [thread overview]
Message-ID: <4759C6C5.2000100@linux.vnet.ibm.com> (raw)
In-Reply-To: <9AEDD952-7F20-471C-9A82-B6F3254BC869@kernel.crashing.org>
Kumar Gala wrote:
>
> On Dec 7, 2007, at 4:12 PM, Balbir Singh wrote:
>
>> Kumar Gala wrote:
>>>
>>> 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
>>
>> Sure. In my case I need to emulate NUMA nodes to do some NUMA specific
>> testing. The memory controller I've written has some interesting data
>> structures like per node, per zone LRU lists. To be able to test those
>> features on a non-numa box is a problem, since we get just the default
>> node.
>
> Maybe I'm missing something, what do you mean by memory controller
> you've written? (I'm use to the term 'memory controller' meaning the
> actual RAM control).
>
Ah! that explains the disconnect. If you look at the latest -mm tree. We
have a memory controller under control groups, we use it to control how
much memory a group of process can access at a time.
>> To be able to test the memory controller under NUMA, I use fake NUMA
>> nodes. x86-64 has a similar feature, the code I have here is the
>> simplest I could come up with for PowerPC.
>>
>> I just thought of another very interesting use case, it can be used to
>> split up the zone's lru lock which is highly contended.
>
> - k
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-12-07 22:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 21:14 [PATCH] Fake NUMA emulation for PowerPC Balbir Singh
2007-12-07 21:28 ` Olof Johansson
2007-12-07 21:35 ` Balbir Singh
2007-12-07 21:55 ` Kumar Gala
2007-12-07 22:12 ` Balbir Singh
2007-12-07 22:15 ` Kumar Gala
2007-12-07 22:18 ` Balbir Singh [this message]
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: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
[not found] ` <20071207221106.GH16824@localdomain>
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=4759C6C5.2000100@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=galak@kernel.crashing.org \
--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;
as well as URLs for NNTP newsgroup(s).