Runtimes (os/hardware-facing)

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)
Does your RTS depend on any specific hardware-specific capability?	(XPRESS)	(TG)	(DEGAS)	(D-TEC)	(DynAX)	(X-TUNE)	(GVR)	(CORVETTE)	N/A	(PIPER)	}