RE: [RFC] XRC upstream merge reboot

Hefty, Sean
2011-07-20T18:51:52Z

I've tried to come up with a clean way to determine the lifetime of an xrc tgt qp, and I think the best approach is still:

1. Allow the creating process to destroy it at any time, and

2a. If not explicitly destroyed, the tgt qp is bound to the lifetime of the xrc domain
or
2b. The creating process specifies during the creation of the tgt qp whether the qp should be destroyed on exit.

The MPIs associate an xrc domain with a job, so this should work. Everything else significantly complicates the usage model and implementation, both for verbs and the CM. An application can maintain a reference count out of band with a persistent server and use explicit destruction if they want to share the xrcd across jobs.

Option 2a is the current implementation, but 2b should be a minor change. I'd like to reach a consensus on the right approach here, since there doesn't appear to be issues elsewhere.

- Sean