Operating Systems: Difference between revisions

Revision as of 16:33, April 29, 2014

Sonia requested that Pete Beckman initiate this page. For comments, please contact Pete Beckman. This page is still in development.

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 are the key system calls / features that you need OS/R to support? Examples: exit, read, write, open, close, link, unlink, chdir, time, chmod, clone, uname, execv, etc.	(EXPRESS)	(TG)	(DEGAS)	(D-TEC)	(DynAX)	(X-TUNE)	(GVR)	(CORVETTE)	SLEEC	(PIPER)
Does your project implement it's own lightweight thread package, or does it rely on the threads provided by the OS/R? If you implement your own threads, what are the key features that required taking on a new implementation? If you don't implement your own thread package, what are the key performance characteristics and APIs needed to support your project?	(EXPRESS)	(TG)	(DEGAS)	(D-TEC)	(DynAX)	(X-TUNE)	(GVR)	(CORVETTE)	N/A	(PIPER)
baz?	(EXPRESS)	(TG)	(DEGAS)	(D-TEC)	(DynAX)	(X-TUNE)	(GVR)	(CORVETTE)	N/A	(PIPER)
buzz?	(EXPRESS)	(TG)	(DEGAS)	(D-TEC)	(DynAX)	(X-TUNE)	(GVR)	(CORVETTE)	N/A	(PIPER)
zoo?	(EXPRESS)	(TG)	(DEGAS)	(D-TEC)	(DynAX)	(X-TUNE)	(GVR)	(CORVETTE)	N/A	(PIPER)

@@ Line 28: / Line 28: @@
 |(PIPER)
 |- style="vertical-align:top;"
-|bar?
+|Does your project implement it's own lightweight thread package, or does it rely on the threads provided by the OS/R? If you implement your own threads, what are the key features that required taking on a new implementation? If you don't implement your own thread package, what are the key performance characteristics and APIs needed to support your project?
 |(EXPRESS)
 |(TG)