Christopher Samuel, le Thu 07 Apr 2011 02:14:31 +0200, a écrit :
> Are these ignorable ?
Yes. Cross-building code without the proper headers just for tests is
never going to work flawlessly :)
Samuel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/11 03:17, Brice Goglin wrote:
> The Hardware Locality (hwloc) team is pleased to
> announce the first release candidate of v1.2:
I get the following warnings when doing a "make check"
on SuSE SLES10 on PPC64 and RHEL5.6 on x86-64:
CC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/11 07:05, Brice Goglin wrote:
> Actually, I am not so familiar with all these marketing
> names, so I don't really know if the "Fusion" name applies
> to Bulldozer chips, or only to the already available
> laptop-like Bobcat chips.
Hello,
What I call "GPU cores" is likely not shown by the operating systems as
"normal" cores. So hwloc would likely not show anything about them. The
new hwloc trunk has support for showing GPU devices (as long as they are
PCI devices), but we won't have any details about the cores inside these
Just wondering if anyone on this list has an AMD fusion laptop, or has
access to a machine with pre-release version of AMD Fusion CPUs?? I
would like to find out what hwloc reports when it is run on those
machines: do the GPU cores get reported as CPU cores or not reported
by hwloc at all?? I
Reminder:
If you are interested in attending the May 3-5 Open MPI Developers Meeting at
ORNL let let Rich (rlgraham -at- ornl -dot- gov) and I know as soon as possible
so we can start the paperwork. This is of particular importance for non-US
citizens since the paperwork takes considerably
Looks like the lifeline is still pointing to its old daemon instead of being
updated to the new one. Look in orte/mca/routed/cm/routed_cm.c - should be
something in there that updates the lifeline during restart of a checkpoint.
On Apr 6, 2011, at 7:50 AM, Hugo Meyer wrote:
> Hi all.
>
> I
Hi all.
I corrected the error with the port. The mistake was because he tried to
start theprocess back and the ports are static, the process was taking a port
where an app was already running.
Initially, the process was running on [[65478,0],1] and then it moves to
[[65478,0],2].
So now i get
On 04/06/2011 08:49 AM, Brice Goglin wrote:
Le 31/03/2011 18:06, Jeff Squyres a écrit :
On Mar 28, 2011, at 5:26 PM, Brice Goglin wrote:
libpci is needed to make this work. And only Linux gives you OS devices
for now (we use sysfs to translate between pci devs and os devs).
Is libpci
Le 31/03/2011 18:06, Jeff Squyres a écrit :
> On Mar 28, 2011, at 5:26 PM, Brice Goglin wrote:
>
>> libpci is needed to make this work. And only Linux gives you OS devices
>> for now (we use sysfs to translate between pci devs and os devs).
>>
> Is libpci available on all platforms? Or is
I'm running into a hang that is very easy to reproduce. Basically,
something like this:
% mpirun -H remote_node hostname
remote_node
^C
That is, I run a program (doesn't need to be MPI) on a remote node. The
program runs, but my local orterun doesn't return. The problem seems
11 matches
Mail list logo
