Supercomputer operating system: Difference between revisions

Revision as of 14:34, 26 February 2012

Revision as of 14:39, 26 February 2012

Line 23:

While in a traditional multi-user computer system, [[job scheduling]] is in effect a [[task scheduling|scheduling]] problem for processing and peripheral resources, in a a massively parallel system, the job management system needs to manage the allocation of both computational and communication resources.<ref name=Yariv /> The need to tune task scheduling and tune the operating system in different configurations of a supercomputer is essential. A typical parallel job scheduler has a [[Master/slave (technology)|master scheduler]] which instructs a number of slave schedulers to launch, monitor and control [[Parallel processing|parallel jobs]], and periodically receives reports from them about the status of job progress.<ref name=Yariv />

The separation of the operating system into separate components was alsobecame necessary as supercomputers developed different types of nodes, e.g. compute nodes vs I/O nodes. AndThus ondifferent theoperating samesystems supercomputer,may be running on different Linux-basednodes OSof maythe besame supercomputer, running, e.g. Craya usesmodern computeCray Linuxsupercomputer onmay someuse nodes,a anotherminimal [[compute Linux]] on anothercompute nodes, and thea "entirelarger OS"Linux isvariant reallyon madeother ofnodes.<ref aname=EuroPar2004/><ref combination of multiple operating systems.name=Alam/>

==Early systems==