Runtimes (os/hardware-facing): Difference between revisions
From Modelado Foundation
imported>Rbbrigh No edit summary |
imported>Schulzm No edit summary |
||
| Line 24: | Line 24: | ||
|(CORVETTE) | |(CORVETTE) | ||
|SLEEC | |SLEEC | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|Does your RTS span the system? If so, what network interface capability does your RTS need? | |Does your RTS span the system? If so, what network interface capability does your RTS need? | ||
| Line 36: | Line 36: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |Tools will have a global "runtime" to collect and aggregate data - this network will be out of band. This will span the whole job. | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|How does your RTS map user-level and OS-level scheduling? | |How does your RTS map user-level and OS-level scheduling? | ||
| Line 48: | Line 48: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|What does your RTS use for locality information? | |What does your RTS use for locality information? | ||
| Line 60: | Line 60: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|What OS or hardware information does your RTS need to monitor and adapt? | |What OS or hardware information does your RTS need to monitor and adapt? | ||
| Line 72: | Line 72: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|Does your RTS require support for global namespace or global address space? | |Does your RTS require support for global namespace or global address space? | ||
| Line 84: | Line 84: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|What local memory management capability does your RTS require? | |What local memory management capability does your RTS require? | ||
| Line 96: | Line 96: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|Does your RTS address external I/O capability? | |Does your RTS address external I/O capability? | ||
| Line 108: | Line 108: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|What interface and/or mechanism is used for the OS to request RTS services? | |What interface and/or mechanism is used for the OS to request RTS services? | ||
| Line 120: | Line 120: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
N/A | |||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|How does your RTS support legacy application or legacy RTS capability? | |How does your RTS support legacy application or legacy RTS capability? | ||
| Line 132: | Line 132: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|Does your RTS depend on any specific hardware-specific capability? | |Does your RTS depend on any specific hardware-specific capability? | ||
| Line 144: | Line 144: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
|( | |Full (and well documented) access to performance counters | ||
| | | | ||
} | } | ||
Revision as of 05:53, May 1, 2014
| QUESTIONS | XPRESS | TG X-Stack | DEGAS | D-TEC | DynAX | X-TUNE | GVR | CORVETTE | SLEEC | PIPER | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| PI | Ron Brightwell | Shekhar Borkar | Katherine Yelick | Daniel Quinlan | Guang Gao | Mary Hall | Andrew Chien | Koushik Sen | Milind Kulkarni | Martin Schulz | |
| What system calls does your RTS currently use? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | SLEEC | N/A | |
| Does your RTS span the system? If so, what network interface capability does your RTS need? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | Tools will have a global "runtime" to collect and aggregate data - this network will be out of band. This will span the whole job. | |
| How does your RTS map user-level and OS-level scheduling? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| What does your RTS use for locality information? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| What OS or hardware information does your RTS need to monitor and adapt? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| Does your RTS require support for global namespace or global address space? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| What local memory management capability does your RTS require? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| Does your RTS address external I/O capability? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| What interface and/or mechanism is used for the OS to request RTS services? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A
N/A | ||
| How does your RTS support legacy application or legacy RTS capability? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A | |
| Does your RTS depend on any specific hardware-specific capability? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | Full (and well documented) access to performance counters |
} |