From: Caspar Zhang <caspar@casparzhang.com>
To: Zhouping Liu <zliu@redhat.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH resend 5/6] mm: use new numa_helper
Date: Fri, 10 Aug 2012 16:22:07 +0800 [thread overview]
Message-ID: <5024C4AF.7020903@casparzhang.com> (raw)
In-Reply-To: <5024BFF9.7050703@redhat.com>
On 08/10/2012 04:02 PM, Zhouping Liu wrote:
> Caspar, I found get_a_numa_node always return the first node id, which
> will make all cases called the function
> only run in the first node, I don't think it's a good way, it decrease
> the coverage.
>
> we should prefer to run cases on the second node, we can chose the first
> only if it just only has
> one node with NH_MEMS|NH_CPUS. do you think so?
>
> and others is good for me.
Jan and I discussed this issue before:
On 08/01/2012 06:23 PM, Jan Stancek wrote:
>>> >> >Do you think it will affect test coverage if we always test first
>>> >> >node?
> > I'm leaning towards "no". I'm assuming oom01 is using default mem
policy,
> > so it can allocate memory from any node (including second one).
And I agree with this opinion. What you think?
Caspar
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-08-10 8:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 6:15 [LTP] [PATCH resend 0/6] NUMA and follow-up fix Caspar Zhang
2012-08-09 6:15 ` [LTP] [PATCH resend 1/6] numa_helper: add flag to get_allowed_nodes() Caspar Zhang
2012-08-10 7:43 ` Zhouping Liu
2012-08-09 6:15 ` [LTP] [PATCH resend 2/6] update testcases to use flag for get_allowed_nodes() Caspar Zhang
2012-08-10 7:45 ` Zhouping Liu
2012-08-09 6:15 ` [LTP] [PATCH resend 3/6] syscalls/numa: check syscall availability Caspar Zhang
2012-08-09 9:22 ` Jan Stancek
2012-08-09 10:35 ` Caspar Zhang
2012-08-10 7:46 ` Zhouping Liu
2012-08-10 7:54 ` Wanlong Gao
2012-08-10 8:13 ` Zhouping Liu
2012-08-09 6:15 ` [LTP] [PATCH resend 4/6] numa_helper: move to libkerntest Caspar Zhang
2012-08-10 3:26 ` [LTP] [PATCH resend 4/6 v2] " Caspar Zhang
2012-08-10 7:51 ` Zhouping Liu
2012-08-09 6:15 ` [LTP] [PATCH resend 5/6] mm: use new numa_helper Caspar Zhang
2012-08-10 8:02 ` Zhouping Liu
2012-08-10 8:22 ` Caspar Zhang [this message]
2012-08-10 8:24 ` Jan Stancek
2012-08-10 9:54 ` Zhouping Liu
2012-08-09 6:15 ` [LTP] [PATCH resend 6/6] mm: add common Makefile include: libmem.mk Caspar Zhang
2012-08-09 10:15 ` [LTP] [PATCH resend 0/6] NUMA and follow-up fix Jan Stancek
2012-08-09 10:31 ` [LTP] [PATCH resend v2 3/6] syscalls/numa: check syscall availability Caspar Zhang
2012-08-10 8:10 ` Zhouping Liu
2012-08-10 3:12 ` [LTP] [PATCH resend 0/6] NUMA and follow-up fix Zhouping Liu
2012-08-10 3:28 ` Caspar Zhang
2012-08-10 3:57 ` Zhouping Liu
2012-08-10 9:22 ` Wanlong Gao
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=5024C4AF.7020903@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=zliu@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.