Hi Brice,
thanks for the info, but it means mbind() function could does not works in
some cases?
2011/8/14 Brice Goglin
> **
> FWIW it's worth, it's a "bug" in valgrind. The manpage of mbind does not
> exactly match the kernel requirements on mbind parameters. And valgrind
> fails at respecting
No it just means that valgrind could properly check how hwloc uses mbind. But I
checked the hwloc code again, things look ok, and the kernel is happy with our
mbind parameters.
Brice
- Reply message -
De : "Gabriele Fatigati"
Pour?: "Brice Goglin"
Cc : "Hardware locality user list"
If I understand well,
there are parameters mismatch between mbind manual and kernel
implementation. It means that if I use mbind() directly and not by hwloc, I
could pass it wrong parameters.. or not?
2011/8/15 Brice Goglin
>
> No it just means that valgrind could properly check how hwloc uses
Gabriele Fatigati, le Mon 15 Aug 2011 10:56:49 +0200, a écrit :
> thanks for the info, but it means mbind() function could does not works in
> some
> cases?
No, valgrind just checks the arguments, it does not change the system
call behavior, so it should just work as usual.
Samuel
Hello,
I'm having the problem that my Magny Cours system is being identified (via
hwloc-ls) as sharing an L3 cache between the NUMAnodes on a single socket. I
know that this is not actually true, and I don't know how to begin debugging
hwloc to see why it thinks that about the L3 cache. Thought
Wheeler, Kyle Bruce, le Tue 16 Aug 2011 00:11:41 +0200, a écrit :
> I'm having the problem that my Magny Cours system is being identified (via
> hwloc-ls) as sharing an L3 cache between the NUMAnodes on a single socket. I
> know that this is not actually true, and I don't know how to begin debugg
