Actions

Runtimes (os/hardware-facing)

From Modelado Foundation

Revision as of 05:53, May 1, 2014 by imported>Schulzm
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

}