@Stevwonder:
During the group meeting (either this week or last week), you mentioned that you think there is a better way to construct/wire-up the hierarchy of Flux instances than what is currently being done in the hierarchical emulator. I was wondering if you could expand on that a bit. I didn’t fully comprehend what you meant during the meeting.
My understanding of the current code is that each Flux instance stores a copy of its handle as well as a handle to its parent (and/or the root instance of the hierarchy). I’m not 100% sure how the child gets the handle to the parent, but I believe the parent’s URI is passed as an argument to the child (who then uses that URI to create a handle).
@garlick (in reply to @stevwonder):
My understanding is that Suraj implemented a dedicated scheduler to scheduler communication mechanism for hierarchical scheduling.