Operating Systems: Difference between revisions
From Modelado Foundation
imported>Beckman No edit summary |
imported>Beckman No edit summary |
||
| Line 28: | Line 28: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|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 | |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 developing 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) | |(EXPRESS) | ||
|(TG) | |(TG) | ||
| Line 40: | Line 40: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |Do you currently view virtualization as a key requirement to support your x-stack project? If so, why? | ||
|(EXPRESS) | |(EXPRESS) | ||
|(TG) | |(TG) | ||
| Line 52: | Line 52: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |What energy/power and reliability APIs do you expect from the OS/R? | ||
|(EXPRESS) | |(EXPRESS) | ||
|(TG) | |(TG) | ||
| Line 64: | Line 64: | ||
|(PIPER) | |(PIPER) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | |Does your project include support for multiple, hierarchical, memory regions? If so, how will it be allocated and managed, by your xstack project or my the OS/R? What APIs do you expect the OS/R to support complex and deep memory? | ||
|(EXPRESS) | |(EXPRESS) | ||
|(TG) | |(TG) | ||
Revision as of 16:43, 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 developing 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) |
| Do you currently view virtualization as a key requirement to support your x-stack project? If so, why? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) |
| What energy/power and reliability APIs do you expect from the OS/R? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) |
| Does your project include support for multiple, hierarchical, memory regions? If so, how will it be allocated and managed, by your xstack project or my the OS/R? What APIs do you expect the OS/R to support complex and deep memory? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) |