Project Status Reports


July, 1996


December, 1995


June 30, 1994

Active participation by:

Additional input from:

The MQM working group was approved in early spring. Work has proceeded concurrently along several veins, as described below.


MQM home page
Parallel Tools at Oregon State home page
Parallel Tools Consortium home page

This document was last updated 13 July '95.

For further information, contact Don Fang, fangy@research.cs.orst.edu.

July 12, 1995

STATUS OF GRAPHICAL TOOL:

A Tk/Tcl graphical interface has been developed in prototype form to show:

INTERFACE BETWEEN IPD AND MQM:

Integration between Intel's IPD and MQM has been successfully completed.


Nov. 8, 1994

STATUS OF GRAPHICAL TOOL:

A Tk/Tcl graphical interface has been developed in prototype form to show:

The primary design questions centered around how to manage the numerous filtering options in a straightforward, self-explanatory way. After testing a variety of mechanisms, we decided to divide filtering options into two types:

With operation-based filtering options, the user can choose to see the status of any combination of sends (blocking and/or non-blocking), messages pending receipt, receives (blocking and/or non-blocking), and indications of barrier waits. With content-based filtering, only those messages matching user-specified sources, destinations, and types will be shown. These filtering mechanisms have been implemented since the last report.

A query manager that is in charge of querying the message passing system and managing the message data has also been implemented. MQM can be hooked up with any message passing systems once their standard format query is implemented.

Next, we will develop a prototype form of lower-level displays. That includes view of pending message operations associated with an individual process, and detailed view of message contents.

The prototype will be demonstrated at the Parallel Tools Consortium booth at SC'94.

STANDARD QUERY FORMAT:

Since the last report, we've simplified the standard format query.


Sept. 14, 1994

STATUS OF GRAPHICAL TOOL:

A Tk/Tcl graphical interface of the system overview presenting information on all processes at a gross scale, and an overview of a subset of processes has been developed in prototype form.

The primary design questions centered around how to manage the numerous filtering options in a straightforward, self-explanatory way. A variety of mechanisms were tested, after user input was employed to develop a user-oriented scheme for grouping messaging operations into logical subsets.

There was also considerable design work in establishing mechanisms that would provide intuitive support for process subset filters. A test version of this was shown to users at NCAR in August, who concurred that the clearest way was to include an explicit how-to message directly in the subset window.

One problem with the user interviews is that, since no existing tool offers "snapshot" views of message queues, users aren't certain how such a facility would be used in typical programming scenarios.

We hope to have a full prototype ready for user feedback by the end of September.

STANDARD QUERY FORMAT:

A draft of the standard queries to be supported by the underlying message system (and the data types required for the queries). To date, discussion has centered around what, if any, assumptions might be made about the process/thread identifier format. Fine-tuning of the query format has not yet begun.

NTERFACE BETWEEN MQM AND AIMS:

An initial draft implementation was made to establish feasibility. This will work for either NX or PVM message passing, as long as the application is instrumented by AIMS's instrumenter and linked with the AIMS monitoring library.

The draft implementation works as follows: Each application sets up an interrupt handler before commencing execution. On request by the user (e.g., via ^C), the application is halted by a signal, triggering activation of a handler which accomplishes the MQM functional operations:

INTERFACE BETWEEN MQM AND IPD:

Although there has been some discussion about this implementation, work has not yet begun.