1. Workload distribution in satellites Final Presentation Performed by :Grossman Vadim Maslovksy Eugene Instructor:Rivkin Inna Spring 2004

2. An introduction Several I/O peripherals require lots of “attention” Degrading the overall performance Some systems should prioritize computational power over I/O latency We were appointed to design a system that would enable that

3. Concept Before Main CPU I/O per. Before : Main CPU deals with ALL the I/O ALL the time! After EV04S (I/O CPU) Main CPU I/O per. After : Main CPU deals ONLY with the device ONLY when needed!

4. What can we improve? Implement the I/O protocols elsewhere – Using an I/O CPU Reduce the number of distractions – Less interrupts – I/O CPU polling – Using Buffers

5. The chosen solution Advantages: – Faster access from the PPC – Less load on the busses Disadvantages: – More complex design – More hardware needed PLBOPB Main CPU I/O CPU PLB2 OPB EV04S

6. Multiple devices How about several I/O peripherals? A unified device 1) Use one “communication line” and protocol Several devices 2) A device for each peripheral 3) Groups of 3 on a single IPIF The 2 nd and 1 st solutions were implemented

7. Architecture diagram DLMB PPC MB I/O #1I/O #2I/O #3 OPB PLB Bram + Controller PLB2OPB ILMB Bram + Controller EV04S EV04S MB IntcPPC Intc EV04S

8. Deeper and deeper IPIF IPIF Control Unit Buffers Unit OPB PLB PPC int. MB int. 64 bits 32 bits

9. The buffers FIFO 64 bits 32 bits MUX 32 bits Control in Asynchronous FIFO cores Double FIFO sets + a mux \ switch

10. Deeper into the buffers One unit for each device A register could be used for behavioral settings FIFO SET PLB2OPB FIFO SET OPB2PLB Controls in/out 64 bits 32 bits Optional Reg.

11. Deeper into the controls PLB Controller FIFO SET PLB2OPB FIFO SET OPB2PLB OPB Controller OPB clk R_req W_req Ack Err Busy PLB clk R_req W_req Ack Err Busy PLB clkOPB clk PLB clkOPB clk W_enAck/ErrFull Count write read R_enAck/ErrEmpty Count W_enAck/ErrFullCount write read R_enAck/ErrEmptyCount MB int. PPC int. PLB IPIF OPB IPIF Retry Wait Empty

12. Deeper into the FIFO set FIFO 1 FIFO 2 64 bits 32 bits MUX 32 bits Controller PLB2OPB set R_en 1 R_en 2 W_en MUX From each FIFO OPB clk PLB clk R_en W_en From upper level R_ackW_ackFullEmpty To upper level Counter R_ack W_ackFull1Empty Counter Controller The controller: Create multiple control signals Manage the read switching Controller

13. Deeper into the FIFO set FIFO 1 FIFO 2 64 bits 32 bits DEC 32 bits Controller OPB2PLB set Controller The controller: Create multiple control signals Manage the write switching Controller OPB clk PLB clk W_en R_en From upper level R_ackW_ackFullEmpty To upper level Counter From each FIFO R_ack W_ackFull1Empty Counter W_en 1 W_en 2 R_en MUX

14. Implemented buffers VHDL HDLDesigner – State machines – Interconnections

15. Block and Stream sets Different sets for different demands Block device set – Large FIFO – Slow response times – 4 byte header with number of packets Stream device set – Small FIFO – Very responsive – Up to 3 data bytes and 1 byte header in each transaction

16. FIFO set driver Implemented functions include: – Read – Write – Empty check Different functions for different sides

17. Issues Expected issues Unexpected issues

18. No full / empty indication Problem: The CPUs are unaware of the Sets’ status Exceptions? Arbitration control - Wait? Retry? Retry ignored by PLB IPIF Retry for OPB, Wait for PLB Prevents crashes in extreme cases

19. Empty Controllers Does not help with Interrupts We must empty the set after any interrupt Must have an empty indicator Empty ports from FIFO sets Accessed via IPIFs on different buses 32 FIFO sets can be connected to one empty controller Asserted between packets

20. Different behavioral settings Different set  Different behavior Multiple cores are cumbersome Change setting via EDK

21. PCI & ALI support Usage of PCI & ALI bridge – Initialization – Configuration Serial Port Driver Two devices conflicts … Timing Problems with SW of MB Thanks to Igor and Leonid for keyboard code and PCI & ALI support Very bad documentation of these issues by and Xillinx

22. Serial Port Driver Driver for both Serial ports – Initialization and configuration function Can choose which of the two ports to initialize Settings configuration for the chosen port – Byte Send/Receive/Check functions – String Send/Receive/FIFO-Check functions

23. Multiple device on ALI Connecting both RS-232 and keyboard – Very heavy conflicting – Sensitive to time, code, optimization, – No suitable help from ALI documentation Made a working project with both I/O – Cannot integrate because of the mentioned problems Borders with the absurd

24. Out of order execution How can we wait (kill time)? – PPC – sleep, usleep – MB – for, while Synchronization is problematic on the MB – Time definitions are not strict Compilers optimization (OOE) – No optimization (IOE)

25. 64 bit transactions PPC 32 bit Architecture PLB supports 64 bit data transactions PPC supports 32/64 bit PLB data interface 64bit transactions made through PPC cache – Needs configuration and much work – A topic for a new project is 64 bit Ready

26. Interrupts… Indicate: – Sufficient data is awaiting – Data awaits sufficient time Behavioral settings – Trigger – Charger – Not empty time out – Write stop time out

27. Current project status PPC and MB system Two settings of buffers (8Kbit \ 256bit) Operation controllers, interrupts UART and virtual I/Os used

28. Demonstration We transmit over 2 channels: – Block FIFO – file or keyboard – Stream FIFO – generated by counter One reads from the UART (keyboard, file) Second, reads from a memory and writes back

29. Performance 1

30. Performance 2 MB cannot handle with fast Interrupts The system stops responding before it becomes useful. For slower interrupts, the time is constant MB is giving advantage in poling

31. Possible future improvements Using the cache to perform 64bit transactions Better / more stable systems with PCI Timing / synchronizations with MB Arbitration issues Burst mode Exceptions

32. Note : the trademarks and registered trademarks of the products appearing in this presentation are hereby recognized as being the property of their respective owners. Thank you for your attention! Thanks