Runtimes (os/hardware-facing): Difference between revisions
From Modelado Foundation
imported>Rbbrigh (Created page with "{| class="wikitable" ! style="width: 200;" | QUESTIONS ! style="width: 200;" | XPRESS ! style="width: 200;" | TG X-Stack ! style="width: 200;" | DEGAS ! style="width: 200;" |...") |
imported>Rbbrigh No edit summary |
||
| Line 14: | Line 14: | ||
| '''PI''' || Ron Brightwell || Shekhar Borkar || Katherine Yelick || Daniel Quinlan || Guang Gao || Mary Hall || Andrew Chien || Koushik Sen || Milind Kulkarni || Martin Schulz | | '''PI''' || Ron Brightwell || Shekhar Borkar || Katherine Yelick || Daniel Quinlan || Guang Gao || Mary Hall || Andrew Chien || Koushik Sen || Milind Kulkarni || Martin Schulz | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |What system calls does your RTS currently use? | ||
|(XPRESS) | |(XPRESS) | ||
|(TG) | |(TG) | ||
| Line 26: | Line 26: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |Does your RTS span the system? If so, what network interface capability does your RTS need? | ||
|(XPRESS) | |(XPRESS) | ||
|(TG) | |(TG) | ||
| Line 38: | Line 38: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |How does your RTS map user-level and OS-level scheduling? | ||
|(XPRESS) | |(XPRESS) | ||
|(TG) | |(TG) | ||
| Line 50: | Line 50: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |What does your RTS use for locality information? | ||
|(XPRESS) | |(XPRESS) | ||
|(TG) | |(TG) | ||
| Line 62: | Line 62: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |What OS or hardware information does your RTS need to monitor and adapt? | ||
|(XPRESS) | |(XPRESS) | ||
|(TG) | |(TG) | ||
| Line 73: | Line 73: | ||
|N/A | |N/A | ||
|(PIPER) | |(PIPER) | ||
|} | |- style="vertical-align:top;" | ||
|Does your RTS require support for global namespace or global address space? | |||
|(XPRESS) | |||
|(TG) | |||
|(DEGAS) | |||
|(D-TEC) | |||
|(DynAX) | |||
|(X-TUNE) | |||
|(GVR) | |||
|(CORVETTE) | |||
|N/A | |||
|(PIPER) | |||
|- style="vertical-align:top;" | |||
|What local memory management capability does your RTS require? | |||
|(XPRESS) | |||
|(TG) | |||
|(DEGAS) | |||
|(D-TEC) | |||
|(DynAX) | |||
|(X-TUNE) | |||
|(GVR) | |||
|(CORVETTE) | |||
|N/A | |||
|(PIPER) | |||
|- style="vertical-align:top;" | |||
|Does your RTS address external I/O capability? | |||
|(XPRESS) | |||
|(TG) | |||
|(DEGAS) | |||
|(D-TEC) | |||
|(DynAX) | |||
|(X-TUNE) | |||
|(GVR) | |||
|(CORVETTE) | |||
|N/A | |||
|(PIPER) | |||
|- style="vertical-align:top;" | |||
|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 | |||
|(PIPER) | |||
|- style="vertical-align:top;" | |||
|How does your RTS support legacy application or legacy RTS capability? | |||
|(XPRESS) | |||
|(TG) | |||
|(DEGAS) | |||
|(D-TEC) | |||
|(DynAX) | |||
|(X-TUNE) | |||
|(GVR) | |||
|(CORVETTE) | |||
|N/A | |||
|(PIPER) | |||
| | |||
} | |||
Revision as of 17:36, April 30, 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 | (PIPER) | |
| 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 | (PIPER) | |
| How does your RTS map user-level and OS-level scheduling? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) | |
| What does your RTS use for locality information? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) | |
| 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 | (PIPER) | |
| Does your RTS require support for global namespace or global address space? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) | |
| What local memory management capability does your RTS require? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) | |
| Does your RTS address external I/O capability? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) | |
| 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 | (PIPER) | |
| How does your RTS support legacy application or legacy RTS capability? | (XPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) |
} |