On Mar 29, 2010, at 5:53 PM, Abhishek Kulkarni wrote:
>
>
> On Mon, 29 Mar 2010, Sylvain Jeaugey wrote:
>
>> Hi Ralph,
>>
>> For now, I think that yes, this is a unique identifier. However, in my
>> opinion, this could be improved in the future replacing it by a unique
>> string.
>>
>> Som
On Mon, 29 Mar 2010, Sylvain Jeaugey wrote:
Hi Ralph,
For now, I think that yes, this is a unique identifier. However, in my
opinion, this could be improved in the future replacing it by a unique
string.
Something like :
#define ORTE_NOTIFIER_DEFINE_EVENT(eventstr, associated_text) {
On Mon, 29 Mar 2010, Ralph Castain wrote:
Hi Abhishek I'm confused by the WDC wiki page, specifically the part
about the new ORTE_NOTIFIER_DEFINE_EVENT macro. Are you saying that I
(as the developer) have to provide this macro with a unique notifier id?
So that would mean that ORTE/OMPI would
Hi Sylvain
I think something like that is really required. Having to manage event
identifiers across OMPI layers is going to prove impractical otherwise.
Abhishek: I would suggest this be done prior to moving the branch into the
trunk. Whether you use Sylvain's proposed solution or another is u
This line of work sounds interesting. Just wanted to add my 2 cents on
one point below.
On Mar 26, 2010, at 9:46 AM, Christoph Konersmann wrote:
The Background:
I should give some background, why I'm implementing this. Changing
the
MPI communication from a high speed network to a netwo
Hi Ralph,
For now, I think that yes, this is a unique identifier. However, in my
opinion, this could be improved in the future replacing it by a unique
string.
Something like :
#define ORTE_NOTIFIER_DEFINE_EVENT(eventstr, associated_text) {
static int event = -1;
if (OPAL_UNL
Process migration is a feature that we are planning on adding to the
1.5 series within the next year. Unfortunately I cannot provide any
more details about the state of the implementation or availability
schedule at the moment. Once it is publicly available then there will
be an announcemen
The link that Jeff cited contains all of the public information about
the current design and use of the C/R infrastructure in Open MPI. The
rest of the design of Open MPI is largely in the source code at the
moment.
If you have questions about the design or specific pieces of code,
then t
Hi Abhishek
I'm confused by the WDC wiki page, specifically the part about the new
ORTE_NOTIFIER_DEFINE_EVENT macro. Are you saying that I (as the developer) have
to provide this macro with a unique notifier id? So that would mean that
ORTE/OMPI would have to maintain a global notifier id count
==
[RFC 2/2]
==
WHAT: Merge the OPAL SOS development branch into the OMPI trunk.
WHY: Bring over some of the work done to enhance error reporting
capabilities
==
[RFC 1/2]
==
WHAT: Merge improvements to the "notifier" framework from the OPAL SOS
and the ORTE WDC mercurial branches into the SVN trunk.
WHY: Some i
11 matches
Mail list logo
