I think the user meant that PelicanHPC lacked clear OMPI-specifc
documentation.
-Paul
Eugene Loh wrote:
I guess a bunch of you already saw this on the lam mail alias. The
part that caught my eye was a user choosing LAM over OMPI due to lack
of "clear documentation" for OMPI.
Origin
I guess a bunch of you already saw this on the lam mail alias. The
part that caught my eye was a user choosing LAM over OMPI due to lack
of "clear documentation" for OMPI.
Original Message
Subject:
LAM: undefined reference to `mpi_bcast__'
On May 28, 2009, at 8:48 AM, Jeff Squyres (jsquyres) wrote:
Yes, the opal-sos branch has a variant of this as well.
One thing I didn't mention: the opal-sos hg tree is unfortunately
unrelated from the main ompi-svn-mirror, so you can't just push/pull
between them. :-(
Most of us OMPI
On May 28, 2009, at 2:55 AM, Nadia Derbey wrote:
Well, it didn't because from what I understood, the MPI program need
to
be changed (register a callback routine for the event, activate the
event, etc), and this is something we wanted to avoid.
Combined with what Terry and Ralph already said
On May 28, 2009, at 7:53 AM, Ralph Castain wrote:
The code in 1.3 is definitely different from the trunk as it lags
quite a bit behind. However, the trunk definitely does include the
code I referenced.
Not sure why the hg mirror wouldn't have it. I would have to defer
to Jeff on that ques
On Thu, 2009-05-28 at 05:57 -0600, Ralph Castain wrote:
> I agree with Terry here about being careful in pursuing this path.
> What I wouldn't want to have happen is to force anyone wanting to be
> notified of error events to have to also turn on peruse, which impacts
> the non-error code path.
Ag
I agree with Terry here about being careful in pursuing this path. What I
wouldn't want to have happen is to force anyone wanting to be notified of
error events to have to also turn on peruse, which impacts the non-error
code path.
Again, I'm not entirely sure what you are trying to do here. As I
The code in 1.3 is definitely different from the trunk as it lags quite a
bit behind. However, the trunk definitely does include the code I
referenced.
Not sure why the hg mirror wouldn't have it. I would have to defer to Jeff
on that question - could be a bug in the update macro that maintains th
On May 28, 2009, at 3:10 AM, Holger Mickler wrote:
> We have a few one-sided tests in the ompi-test repository (which I
think
> Dresden has access to?), but I'm not 100% sure that they're
correct...
Yes, we do have access. We'll try the tests and see how far we can
get :)
Look in ompi
Nadia Derbey wrote:
On Wed, 2009-05-27 at 14:25 -0400, Jeff Squyres wrote:
Excellent points; Ralph and I chatted about this on the phone today --
we concur with George.
Bull -- would peruse work for you? I think you mentioned before that
it didn't seem attractive to you.
Well, it
To be more complete, we pull Hg from
http://www.open-mpi.org/hg/hgwebdir.cgi/ompi-svn-mirror/ ; are we
mistaken ?
If not, the code in v1.3 seems to be different from the code in the trunk
...
Sylvain
On Thu, 28 May 2009, Nadia Derbey wrote:
On Tue, 2009-05-26 at 17:24 -0600, Ralph Castain
On Tue, 2009-05-26 at 17:24 -0600, Ralph Castain wrote:
> First, to answer Nadia's question: you will find that the init
> function for the module is already called when it is selected - see
> the code in orte/mca/base/notifier_base_select.c, lines 72-76 (in the
> trunk.
Strange? Our repository is
Jeff Squyres wrote:
> On May 27, 2009, at 6:49 AM, Holger Mickler wrote:
>
>> would you mind sharing this patch? We'd like to test our current VT
>> version with
>> some MPI RMA code :)
>>
>
> No problem-o. I've submitted this patch upstream to Intel as well.
> Note that the patch slightly ch
On Wed, 2009-05-27 at 14:25 -0400, Jeff Squyres wrote:
> Excellent points; Ralph and I chatted about this on the phone today --
> we concur with George.
>
> Bull -- would peruse work for you? I think you mentioned before that
> it didn't seem attractive to you.
Well, it didn't because from w
14 matches
Mail list logo
