Run-control migration from single book to multibooks


This paper describes the migration of the hardwareimplemented run-control functions from a single-book structure with one flexible service processor (FSP) and one service element (SE) per system to a multibook structure with one FSP per book and one SE per system. The new system structure required two new interfaces between the clock chips on the different books. The first interface is required for dynamic configuration data exchange between books. The alternative path via the SE would not meet the performance requirements. This interface is available in the initial millicode load flow before the L2 caches with their ring structure are operational. Another requirement is the necessity of starting and stopping all books synchronously. The second additional interface between the clock chips on different books enables this function. Nevertheless, the hardware implementation is so flexible that each book may operate independently of the other books. The clock chips are connected as a peer-to-peer network, so no special master is necessary in the system.

DOI: 10.1147/rd.483.0339

Extracted Key Phrases

7 Figures and Tables

Cite this paper

@article{Webel2004RuncontrolMF, title={Run-control migration from single book to multibooks}, author={Tobias Webel and Thomas E. Gilbert and Dietmar Schmunkamp}, journal={IBM Journal of Research and Development}, year={2004}, volume={48}, pages={339-346} }