Skip to content

Conversation

@rhc54
Copy link
Contributor

@rhc54 rhc54 commented Jul 7, 2017

Still only used if rml_ofi_desired=1

@rhc54
Copy link
Contributor Author

rhc54 commented Jul 7, 2017

@anandhis

@anandhis
Copy link
Contributor

anandhis commented Jul 7, 2017

Does this fix the orte_no_op over ofi ?

@rhc54
Copy link
Contributor Author

rhc54 commented Jul 7, 2017

Yes - I've been launching MPI jobs with it just fine. One of the builds in Jenkins is failing, though, so I'm trying to track that down

@rhc54
Copy link
Contributor Author

rhc54 commented Jul 7, 2017

hmmm...I can't make it fail. I wonder if this is something peculiar to suse?

@bwbarrett Is there any way to get more debug info out of that build? I've tried building with the same config, forcing various components off, etc. - to no avail. However, I don't have a suse build.

Ralph Castain added 2 commits July 20, 2017 21:01
…for the daemons. Cleanup the current confusion over how connection info gets created and

passed to make it all flow thru the opal/pmix "put/get" operations. Update the PMIx code to latest master to pickup some required behaviors.

Remove the no-longer-required get_contact_info and set_contact_info from the RML layer.

Add an MCA param to allow the ofi/rml component to route messages if desired. This is mainly for experimentation at this point as we aren't sure if routing wi
ll be beneficial at large scales. Leave it "off" by default.

Signed-off-by: Ralph Castain <rhc@open-mpi.org>
Signed-off-by: Ralph Castain <rhc@open-mpi.org>
@rhc54 rhc54 merged commit 325778e into open-mpi:master Jul 21, 2017
@rhc54 rhc54 deleted the topic/ofi branch July 21, 2017 12:46
PMIX_DESTRUCT(&pbkt);
return rc;
}
<<<<<<< c632784ca34c467055eadcb4efe84a25e5a3911b:opal/mca/pmix/pmix2x/pmix/src/dstore/pmix_esh.c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

}
}

<<<<<<< c632784ca34c467055eadcb4efe84a25e5a3911b:opal/mca/pmix/pmix2x/pmix/src/dstore/pmix_esh.c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rhc54 - looks like unresolved merge

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nah, looks like i just missed removing the last line of the conflict flag - i can clean that up

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw multiple of them and there was clearly an unresolved merges.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure that last part is true, but no matter - it runs just fine and passed an MTT scan, so I think things resolved correctly. Anyway, I'm updating from tarball now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

relax dude - do you not see the .pmix_ignore in that component? It is prevented from compiling due to the reported problems in the dstore. I am removing the ignore now as it seems functional, albeit the memory footprint problem remains

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What memory footprint problem? Is there any issue on that?
I think that @karasevb have fixed (at least) one of the possible causes he discovered when keys was sent in the message from the server to the client even if the dstore was used.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look at the issue he filed this morning in PMIx

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, thanks. I thought it's something else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants