Skip to Content.
Sympa Menu

charm - Re: [charm] running the ibverbs version of charm++

charm AT lists.cs.illinois.edu

Subject: Charm++ parallel programming system

List archive

Re: [charm] running the ibverbs version of charm++


Chronological Thread 
  • From: "Kale, Laxmikant V" <kale AT cs.uiuc.edu>
  • To: Eric Bohm <ebohm AT illinois.edu>, Vlad Cojocaru <Vlad.Cojocaru AT eml-r.villa-bosch.de>
  • Cc: "charm AT cs.uiuc.edu" <charm AT cs.uiuc.edu>
  • Subject: Re: [charm] running the ibverbs version of charm++
  • Date: Mon, 4 Aug 2008 11:39:14 -0500
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/charm>
  • List-id: CHARM parallel programming system <charm.cs.uiuc.edu>

Also, please be aware that ibvrbs is a recent addition, and may not have all
bugs ironed out.
You can also use the mpi version, assuming you machine supports MPI.

Sanjay

-----Original Message-----
From:
charm-bounces AT cs.uiuc.edu

[mailto:charm-bounces AT cs.uiuc.edu]
On Behalf Of Eric Bohm
Sent: Monday, August 04, 2008 11:31 AM
To: Vlad Cojocaru
Cc:
charm AT cs.uiuc.edu
Subject: Re: [charm] running the ibverbs version of charm++

The immediate cause for this is a corruption of data in the received
message. Initnode messages are among the earliest sent, so if something
has gone wrong with ibverbs qpair setup this would be a likely place for
it to crop up.

The usual first point of failure with ibverbs is a problem pinning
memory. Try adding -memory os -thread uJcontext to the link line and
rebuild megatest.

Vlad Cojocaru wrote:
> Dear all,
>
> I successfully built charm++ (the cvs code) for net-linux-amd64 with
> ibverbs option. However when I try to run the megatest I get an error
> "Charmrun: Bad initnode data length. Aborting".
>
> Does anybody have an idea why this happens ?
>
> Thanks
> Best
> vlad
>
>

_______________________________________________
charm mailing list
charm AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/charm





Archive powered by MHonArc 2.6.16.

Top of Page