From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] NUMA system and get_a_numa_node()
Date: Fri, 28 Nov 2014 14:44:30 +0800 [thread overview]
Message-ID: <20141128064430.GC16235@localhost.localdomain> (raw)
In-Reply-To: <5476DCA3.5000701@cn.fujitsu.com>
On Thu, Nov 27, 2014 at 04:11:15PM +0800, Wanlong Gao wrote:
> On 11/27/2014 03:45 PM, Han Pingtian wrote:
> >>
> >>
> >> Do you think ONLY ONE NODE can be called NUMA?
> >>
> >> http://en.wikipedia.org/wiki/Non-uniform_memory_access
> >>
> >
> > I think it's not a problem to run the testcase on a non-NUMA system, if
> > we take it as a special case?
>
> It's meaningless, the "special case" you said is already there, it's ksm01.
>
All right. I hope I can figure out what features is ksm02 testing.
But looks like ksm02 tests "set_mempolicy()" and "cpuset", which ksm01
doesn't deal with. Isn't there any meanings to test them on a single
node system?
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
prev parent reply other threads:[~2014-11-28 7:03 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
2014-11-27 7:45 ` Han Pingtian
2014-11-27 8:11 ` Wanlong Gao
2014-11-28 6:44 ` Han Pingtian [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=20141128064430.GC16235@localhost.localdomain \
--to=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