Figure 4: The Catamount Software Architecture Figure 3: The Blue Gene/L Software Architecture Figure 5: Linux Services oped for Linux. In some cases, these applications may also benefit from the availability of commodity net- working protocols that can be used to interface with remote services (e.g., visualization servers). While they may benefit from some of the Linux ecosystem, it is clear that these applications will not benefit from large parts of this ecosystem. For example, applica- tions running on the compute nodes of a large system are unlikely to need a text editor, terminal emulator, or mail client. Figure 6 presents the software archi- tecture of Linux as this architecture is likely to be used on the compute nodes of a very large system. Figure 9: A More Realistic Approach to Running Linux on Catamount quests. While the PCT can easily provide the needed functionality, it does not currently provide this func- tionality for Catamount applications. In particular, while the PCT can create address maps and run con- texts, it does not make this functionality available to applications. To do so, will require some extensions to the PCT, indicated by the “Xen Wedge.” The QK should not require any modifications. Address faults and exceptions encountered by XenoLinux (for exam- ple, during an attempt to modify an MMU register) would be forwarded to the PCT, where they can be handled in the appropriate manner.
Connect with 287M+ leading minds in your field
Discover breakthrough research and expand your academic network
