From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Han Pingtian <hanpt@linux.vnet.ibm.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] NUMA system and get_a_numa_node()
Date: Thu, 27 Nov 2014 11:06:15 +0800 [thread overview]
Message-ID: <54769527.4020603@cn.fujitsu.com> (raw)
In-Reply-To: <20141127024241.GA16235@localhost.localdomain>
On 11/27/2014 10:42 AM, Han Pingtian wrote:
> On Wed, Nov 26, 2014 at 01:53:36PM +0100, Cyril Hrubis wrote:
>> Hi!
>>> We have a system which only has one NUMA node. When trying to run ksm02
>>> on it, becase the code calling get_allowed_nodes() with a count 2 as
>>> below:
>>>
>>> 972 /* Warning: *DO NOT* use this function in child */
>>> 973 unsigned int get_a_numa_node(void (*cleanup_fn) (void))
>>> 974 {
>>> 975 unsigned int nd1, nd2;
>>> 976 int ret;
>>> 977
>>> 978 ret = get_allowed_nodes(0, 2, &nd1, &nd2);
>>> 979 switch (ret) {
>>> 980 case 0:
>>> 981 break;
>>> 982 case -3:
>>> 983 tst_brkm(TCONF, cleanup_fn, "requires a NUMA system.");
>>>
>>> it always failed with "requires a NUMA system.".
>>>
>>> I think a NUMA system may have only one node, right? If so, could we
>>> change the count to 1?
>>
>> Hmm, are you sure that the testcases are actually applicable to a system
>> with only one node?
>>
>> Because what the testcases do in the setup is to write 1 to
>> /sys/kernel/mm/ksm/merge_across_nodes so I would expect that the test
>> needs at least two nodes...
>>
> I think if there is only one NUMA node, then this is a special case for
> this testcase, it'll test if set "merge_across_nodes" to 1, any problem
> will be triggered.
>
> I have tried to change the node count to 1 in get_allowed_nodes() and
> recompiled ksm02. It works successfully.
>
Do you think ONLY ONE NODE can be called NUMA?
http://en.wikipedia.org/wiki/Non-uniform_memory_access
Thanks,
Wanlong Gao
> Thanks.
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-11-27 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 7:13 [LTP] NUMA system and get_a_numa_node() Han Pingtian
2014-11-26 12:53 ` Cyril Hrubis
2014-11-27 2:42 ` Han Pingtian
2014-11-27 3:06 ` Wanlong Gao [this message]
2014-11-27 7:45 ` Han Pingtian
2014-11-27 8:11 ` Wanlong Gao
2014-11-28 6:44 ` Han Pingtian
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=54769527.4020603@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=hanpt@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.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