Operating Systems: Difference between revisions
From Modelado Foundation
imported>Beckman No edit summary |
imported>Schulzm No edit summary |
||
| Line 26: | Line 26: | ||
|(CORVETTE) | |(CORVETTE) | ||
|SLEEC | |SLEEC | ||
| | |sockets, ptrace access, dynamic linking, timer interrupts/signals, access to hardware counters, file I/O | ||
|- 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 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? | |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? | ||
| Line 38: | Line 38: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |relying on native threads, typically pthreads, which is appropriate | ||
|- 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? | |Do you currently view virtualization as a key requirement to support your x-stack project? If so, why? | ||
| Line 50: | Line 50: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |No | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|What energy/power and reliability APIs do you expect from the OS/R? | |What energy/power and reliability APIs do you expect from the OS/R? | ||
| Line 62: | Line 62: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
|( | |Power: Power measurements at varying granularity using processor internal counters and external sensors, for autotuning access to setting DVFS levels or power capping; Resilience: access to fault notification (for corrected and non-corrected errors) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|Please describe how parallel programs are "composed" within your project, and what APIs and support is required from the OS/R? | |Please describe how parallel programs are "composed" within your project, and what APIs and support is required from the OS/R? | ||
| Line 74: | Line 74: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|What is your model for extreme-scale I/O, and how do you expect the OS/R to support your plans? | |What is your model for extreme-scale I/O, and how do you expect the OS/R to support your plans? | ||
| Line 86: | Line 86: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |For PIPER this refers to performance information: hierarchical aggregation through MRNet to reduce data and perform online analysis. OS support required for bootstrapping / optionally, could be integrated with OS backplanes | ||
|- 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? | |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? | ||
| Line 98: | Line 98: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|} | |} | ||
Revision as of 03:58, May 7, 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 | sockets, ptrace access, dynamic linking, timer interrupts/signals, access to hardware counters, file I/O |
| 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 | relying on native threads, typically pthreads, which is appropriate |
| 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 | No |
| 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 | Power: Power measurements at varying granularity using processor internal counters and external sensors, for autotuning access to setting DVFS levels or power capping; Resilience: access to fault notification (for corrected and non-corrected errors) |
| Please describe how parallel programs are "composed" within your project, and what APIs and support is required from the OS/R? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| What is your model for extreme-scale I/O, and how do you expect the OS/R to support your plans? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | For PIPER this refers to performance information: hierarchical aggregation through MRNet to reduce data and perform online analysis. OS support required for bootstrapping / optionally, could be integrated with OS backplanes |
| 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 | N/A |