1 / 11

Tinkernet

Tinkernet. Dan Turner, Mark Kegel, Erik Shimshock and Ryan Ausanka-Crues With Support and Encouragement by Titus Winters, Mike Erlinger, (also Jason Arold). Don’t pay attention to this comment!. Project Overview. What is Tinkernet?

herne
Télécharger la présentation

Tinkernet

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tinkernet • Dan Turner, Mark Kegel, Erik Shimshock and • Ryan Ausanka-Crues • With Support and Encouragement by • Titus Winters, Mike Erlinger, • (also Jason Arold) Don’t pay attention to this comment!

  2. Project Overview • What is Tinkernet? • System to allow students to write the networking code of an OS • Why would you want it? • Provides a convenient and controlled environment to write and test networking code

  3. How it works... Students Nodes Tinkerbell SSH

  4. Hardware • Rack of nodes • Basic (old) computer • minimal components (RAM, CPU, etc.) • Two network cards • Couple of hubs, many ethernet cables • Server • Standard computer (lots of RAM) • Linux

  5. Student Assignments • Writing modules to handle the protocol stack • ethernet, IP, UDP, ARP • Scaled down version of TCP

  6. Student Perspective • (1) Student writes code • (2) Student compiles code into kernel • (3) Student uses tinkerboot to load kernel • (4) Student tests kernel • (5) Kernel malfunctions, and student goes back to step (1)

  7. Behind the Scenes:Compiling the Kernel • OSKit • provides a fully operable kernel • we strip out the networking module • student code gets compiled in as the new networking module • then you have your kernel...

  8. Behind the Scenes:Booting the Kernel • tinkercontroller • is a daemon that manages the nodes • a free node is chosen, and the kernel is sent to it • if all has gone well, you have a running kernel

  9. The Running Kernel • Kernels are expected to respond to: • ARP requests • IP broadcast • Handle IP packets • UDP protocol • Also need to be able to generate their own packets

  10. Things left to do... • Investigate/implement a less hacked initial node bootup • Documentation... • Portability... • Packaging for distribution...

  11. Questions? • Special Thanks to: • Costco • Backgammon • Air Conditioning

More Related