1. 4/19/20021 TCPSplitter: A Reconfigurable Hardware Based TCP Flow Monitor David V. Schuehler

2. 4/19/20022 Outline Motivation Target Platform Design Possible Applications Results Conclusion

3. 4/19/20023 MOTIVATION

4. 4/19/20024 Why work with TCP? Over 85% on internet traffic is TCP based Internet is growing TCP is a proven reliable transport for data delivery Provide high speed active networks the ability work with TCP flows

5. 4/19/20025 Why not implement a full TCP stack in hardware? Complex protocol stack Several interactions on client interface (sockets?) Difficult to achieving high performance Large memories required for reassembly Limited number of simultaneous connections

6. 4/19/20026 Solution Develop TCP flow monitor - TCPSplitter Utilize existing hardware infrastructure (FPX) Expand upon Layered Protocol Wrappers

7. 4/19/20027 TARGET PLATFORM

8. 4/19/20028 Configuration

9. 4/19/20029 Washington University Gigabit Switch

10. 4/19/200210 FPX Module

11. 4/19/200211 FPX Internal Structure RAD: Reprogrammable Application Device Xilinx XCV1000E FPGA External SRAM/SDRAM Reprogrammable NID: Network Interface Device XCV600E FPGA Controls FPX Programs RAD Forwards traffic

12. 4/19/200212 DESIGN

13. 4/19/200213 Goals High Speed Design Small FPGA Footprint Simple Client Interface Support Large Number of Flows

14. 4/19/200214 Challenges Dealing with dropped frames Packet reordering Maintaining state for large number of flows Developing an efficient implementation Processing data at line rates Minimizing resource requirements

15. 4/19/200215 Assumptions/Limitations All frames must flow through switch Frames traversing in opposite direction handled as separate flow In-order processing of frames for each flow

16. 4/19/200216 TCPSplitter Data Flow

17. 4/19/200217 Input Processing Flow Classification TCP Checksum Engine Input State Machine Control FIFO Frame FIFO Output State Machine

18. 4/19/200218 Layout

19. 4/19/200219 Packet Routing Decisions Forward to outbound IP stack only Forward to both Client App and outbound IP stack Discard packet

20. 4/19/200220 Packet Routing Non-TCP packets  IP stack Invalid TCP checksum  drop TCP SYN packets  IP stack (Seq # < Expected Seq #)  IP stack (Seq # > Expected Seq #)  drop Else  client AND IP stack

21. 4/19/200221 Client Interface 1 bit Clock 1 bit Reset 32 bit Data Word 1 bit Data Enable 4 bit Start/End of Data Signals 2 bit Valid Data Bytes N bit Flow Identifier 2 bit Start/End of Flow Signals 1 bit TCA Client Application

22. 4/19/200222 POSSIBLE APPLICATIONS

23. 4/19/200223 Possible Application 1 Simultaneous update of multiple active network nodes

24. 4/19/200224 Possible Application 2 Dynamic loading of customizable QoS algorithms

25. 4/19/200225 Possible Application 3 Monitoring content of all TCP flows for security

26. 4/19/200226 RESULTS

27. 4/19/200227 Synthesis Results for Xilinx XCV1000E-7 TCPSplitterFull Wrappers (Cell + Frame + IP + TCP + Client) Space/LUTs617 (2%)4954 (20%) Register bits503 (2%)4933 (20%) Input processing delay 7 clock cycles *44-68 clock cycles * * Plus length of packet in 32 bit words

28. 4/19/200228 Sample Run Start of frame Byte count IP payload TCP payload End of frame Flow ID

29. 4/19/200229 Current State of Research Developed and simulated design Handles 256 simultaneous flows  33 bits * 256 entries = 1,056 bytes Synthesizes at 74MHz Simple test client counts TCP data bytes

30. 4/19/200230 Future Directions Execute design in hardware Increase the number of simultaneous flows  262,144 flows require only 1 MByte (+) RAM Develop more elaborate client applications Improve processing performance Implement sliding window – passive solution Enhance frame generation utility for simulations

31. 4/19/200231 CONCLUSION

32. 4/19/200232 Conclusion Runs on reconfigurable hardware platform Process packets at Gigabit line rates Monitors all TCP flows Generates proper byte stream for each flow Requires only minimal memory (33 bits/flow) Simple client interface demonstrated

33. 4/19/200233 Acknowledgments Advisor: Dr. John Lockwood

34. 4/19/200234 Questions