From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jakub Jelen <jakuje@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
trivial@kernel.org, Jakub Jelen <jjelen@redhat.com>
Subject: Re: [PATCH] perf bench numa: Fix assertion for nodes bitfield
Date: Mon, 21 Mar 2016 17:49:07 -0300 [thread overview]
Message-ID: <20160321204907.GA25862@kernel.org> (raw)
In-Reply-To: <1458388687-24421-1-git-send-email-jakuje@gmail.com>
Em Sat, Mar 19, 2016 at 12:58:07PM +0100, Jakub Jelen escreveu:
> Comparing bits and bytes in numa benchmark assertion
>
> I hit the issue on two socket Power8 machine presenting its numa nodes as
> 0,1,16,17 (according to numactl). Therefore I got error
> (and hang of parent process):
>
> perf: bench/numa.c:296: bind_to_memnode: Assertion `!(g->p.nr_nodes > (int)sizeof(nodemask))' failed.
>
> This is obviously false positive. We can fit all the 18 nodes into
> bitfield of 8 bytes (long on 64b architecture).
>
> Signed-off-by: Jakub Jelen <jakuje@gmail.com>
> ---
> Hello kernel list.
> This is my first patch for kernel, so if I missed some of the guidelines,
> please be patient :) I hope everything is explained in the commit message.
Very good start then, I saw no problems, you looked at existing
changesets (I guess), even capitalizing the first word after "perf bench
numa: "! 8-)
Looks fine, applied, thanks.
- Arnaldo
> Thanks,
> Jakub
>
> tools/perf/bench/numa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/bench/numa.c b/tools/perf/bench/numa.c
> index 870b7e6..5276b24 100644
> --- a/tools/perf/bench/numa.c
> +++ b/tools/perf/bench/numa.c
> @@ -293,7 +293,7 @@ static void bind_to_memnode(int node)
> if (node == -1)
> return;
>
> - BUG_ON(g->p.nr_nodes > (int)sizeof(nodemask));
> + BUG_ON(g->p.nr_nodes > (int)sizeof(nodemask)*8);
> nodemask = 1L << node;
>
> ret = set_mempolicy(MPOL_BIND, &nodemask, sizeof(nodemask)*8);
> --
> 2.5.0
next prev parent reply other threads:[~2016-03-21 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 11:58 [PATCH] perf bench numa: Fix assertion for nodes bitfield Jakub Jelen
2016-03-21 20:49 ` Arnaldo Carvalho de Melo [this message]
2016-03-24 7:37 ` [tip:perf/urgent] " tip-bot for Jakub Jelen
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=20160321204907.GA25862@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jakuje@gmail.com \
--cc=jjelen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=trivial@kernel.org \
/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