Content deleted Content added
No edit summary |
Could link to Portals network programming API as I created it. Use non-acronym directly in page? Fixed date errors - assume right way? Maybe add dates if known? |
||
Line 5:
| publisher = Proceedings of the 2006 ACM/IEEE International Conference for High-Performance Computing, Networking, Storage, and Analysis (SC’06)
| author = Moreira, Jose, et al
|
}}</ref>
The [[Cray XT4]] and [[Cray XT5]] supercomputers run [[Compute Node Linux]].<ref name=cnl-dwb>{{cite journal
| title = Compute Node Linux: Overview, progress to date, and roadmap
| publisher = Proceedings of the 2007 Cray User Group Annual Technical Conference
| author =
|
}}</ref> [[Sandia National Laboratories]] has an almost two-decade commitment to Lightweight Kernels on its high-end HPC systems.<ref name=lwk-rr>{{cite journal
| title = Designing and Implementing Lightweight Kernels for Capability Computing
| publisher = Concurrency and Computation: Practice and Experience
| author = Riesen, Rolf, et al
|
}}</ref>
Sandia and University of New Mexico researchers began work on [[SUNMOS]] for the [[Intel Paragon]] in the early 1990s. This operating system evolved into the Puma, Cougar, and Catamount operating systems deployed on [[ASCI Red]] and [[Red Storm (computing)|Red Storm]]. Sandia continues its work in LWKs with a new R&D effort, called kitten .<ref name=pedretti>{{cite web
Line 32:
| title = Software Architecture of the Light Weight Kernel, Catamount
| publisher = Proceedings of the 2005 Cray User Group Annual Technical Conference
| author =
|
}}</ref>
LWK implementations vary, but all strive to provide applications with predictable and maximum access to the [[CPU]] and other system resources. To achieve this, simplified algorithms for scheduling and memory management are usually included. System services (e.g. daemons), are limited to the absolute minimum. Available services, such as job launch are constructed in a hierarchical fashion to ensure scalability to thousands of nodes. Networking protocols for communication between nodes in the system are also carefully selected and implemented to ensure scalability. One such example is the [[Portals network programming
Lightweight Kernel operating systems assume access to a small set of nodes that are running full-service operating systems to offload some of the necessary services: login access, compilation environments, batch job submission, and file I/O.
| |||