On Mar 5, 2008, at 1:50 PM, Greg Watson wrote:
Looking back through the mailing list, I can only see two references
that seem relevant to this. One was titled "Major reduction in ORTE"
and does allude to the event model changes. The other "OMPI/ORTE and
tools" talks about "alternative methods of
On Mar 5, 2008, at 7:38 AM, Jeff Squyres wrote:
On Mar 4, 2008, at 5:44 PM, Greg Watson wrote:
I certainly don't (nor anyone in PTP as far as I know) have the
resources to re-add functionality to OMPI, so unfortunately it
appears
that 1.2 will be the end of the line for PTP supported versi
On Mar 4, 2008, at 5:44 PM, Greg Watson wrote:
I certainly don't (nor anyone in PTP as far as I know) have the
resources to re-add functionality to OMPI, so unfortunately it appears
that 1.2 will be the end of the line for PTP supported versions. As I
mentioned to Ralph, I don't follow your deve
I'll try to get the code into the trunk before I go on vacation for a week
on Fri. If not, I'll let you know and get it the week I get back (3/17).
Basically, all I do is define an event in our event library that "fires" to
send a message to you when the defined trigger occurs.
If that is all you
Ralph,
Looking at PTP, the only thing we need is to query the process
information (PID, rank, node) when the job is created. Perhaps if only
queries are allowed from callbacks then recursion would be eliminated?
If you can get this functionality into your new interface and back in
the tru
Yeah, the problem we had in the past was:
1. something would trigger in the system - e.g., a particular job state was
reached. This would cause us to execute a callback function via the GPR
2. the callback function would take some action. Typically, this involved
sending out a message or calling
I don't have a problem using a different interface, assuming it's
adequately supported and provides the functionality we need. I presume
the recursive behavior you're referring to is calling OMPI interfaces
from the callback functions. Any event-based system has this issue,
and it is usuall
I certainly don't (nor anyone in PTP as far as I know) have the
resources to re-add functionality to OMPI, so unfortunately it appears
that 1.2 will be the end of the line for PTP supported versions. As I
mentioned to Ralph, I don't follow your developer discussions closely
enough to unders
It is buried deep-down in the thread, but I'll just reiterate it here. I
have "restored" the ability to "subscribe" to changes in job, proc, and node
state via OMPI's tool interface library. I have -not- checked this into the
trunk yet, though, until the community has a chance to consider whether o
Greg --
I admit to being a bit puzzled here. Ralph sent around RFCs about
these changes many months ago. Everyone said they didn't want this
functionality -- it was seen as excess functionality that Open MPI
didn't want or need -- so it was all removed.
As such, I have to agree with Ral
10 matches
Mail list logo
