A dedicated kernel named TORO. Matias Vara Larsen

Size: px

Start display at page:

Download "A dedicated kernel named TORO. Matias Vara Larsen"

Hector Hunt
5 years ago
Views:

1 A dedicated kernel named TORO Matias Vara Larsen

2 Who am I? Electronic Engineer from Universidad Nacional de La Plata, Buenos Aires, Argentina. Argentina PhD in Computer Science at INRIA / CNRS, Nice, France (finishing in 2015). I am the main (and the only ;)) developer of TORO

3 What is TORO OS? TORO OS started in 2003, and in 2004, I released the first stable version. FAT12 Filesystem Virtual Filesystem fat12 User applications e.g., shell, ls, echo, etc Scheduler multitasking Paging Memory Device Driver floppy disk TORO OS kernel Hardware (x86) TORO 1.1.3

4 TORO shell

5 LS

6 LS But in that moment, TORO developing was only for fun

7 How we can optimize a general purpose kernel for a given purpose? i.e., application-oriented What is TORO OS? TORO OS starts in 2003, and in 2004, I released the first stable version. FAT12 Filesystem Virtual Filesystem fat12 User applications e.g., shell, ls, echo, etc Scheduler multitasking Paging Memory Device Driver floppy disk TORO OS kernel Hardware (x86) TORO 1.1.3

8 What is TORO kernel? In 2006, the kernel is optimized to run a single user application in a multicore environment

9 What is TORO kernel? In 2006, the kernel is optimized to run a single user application in a multicore environment This defines the architecture of TORO

10 What is TORO kernel? In 2006, the kernel is optimized to run a single user application in a multicore environment TORO TORO integrates integrates the the user user application application with with the the kernel, kernel, and and dedicates dedicates resources resources to to aa given given core core e.g., e.g., memory, memory, devices devices and and so so on on This defines the architecture of TORO

11 Kernel + user application Only ring 0 The application is compiled with the kernel No syscalls, only calls. Threads instead of process Flat memory, no pagination Light context switching In this sense, TORO is a library OS-like designing.

12 Kernel + user application Only ring 0 The application is compiled with the kernel No syscalls, only calls. Memory space in TORO Threads instead of process Flat memory, no pagination Toro kernel + application Light context switching In this sense, TORO is a library OS-like designing. Free Memory

13 Dedicated Resources In a multicore system the problematic resource is the shared memory. The use of shared memory causes: Overhead in the memory bus. Overhead in the cache to keep it coherent. Overhead in spin locks for mutual exclusion.

14 Dedicated Resources In a multicore system the problematic resource is the shared memory. The use of shared memory causes: Overhead in the memory bus. Overhead in the cache to keep it coherent. Overhead in spin locks for mutual exclusion. TORO tries to avoid these problems by keeping all the resources locals, e.g., memory, filesystem

15 Dedicated Memory Allocation Memory space in Toro TORO Memory allocator Core1 Core2 Core3

16 This must be provided by a techno like Dedicated Memory Allocation Intel QuickPath or Hypertransport. Memory space in Toro Memory Region 1 Memory Region 2 Memory Region 3 TORO Memory allocator Core1 Core2 Core3

17 Dedicated Memory Allocation Memory space in Toro Memory Region 1 Memory Region 2 Memory Region 3 TORO Memory allocator ge em tm ro o T () Thread 1 Thread2 Thread3 Core1 Core2 Core3

18 Dedicated Memory Allocation Memory space in Toro Memory Region 1 Memory Region 2 Memory Region 3 In TORO, the memory allocation is always local TORO Memory allocator ge em tm ro o T () Thread 1 Thread2 Thread3 Core1 Core2 Core3

19 Locality of memory Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3

20 Locality of resources i d de c Disk1 Disk2 Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3 Network1 es t a

21 Locality of resources Disk1 i d de c Disk2 Network1 es t a DedicateBlockDriver(Disk1, Core1) DedicateBlockDriver(Disk2, Core2) Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3

22 Locality of resources Network1 i d de c es t a DedicateNetwork(Core3, Network1) Disk1 Disk2 Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3

23 Locality of resources Disk1 Disk2 Network card Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3

24 Locality of resources EXT3 FAT32 Stack TCP/IP Disk1 Disk2 Network card Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3

25 Locality of resources By dedicating resources, TORO avoids the using of Spin locks since there is no acces from others cores. EXT3 FAT32 Stack TCP/IP Disk1 Disk2 Network card Memory 1 Memory 2 Memory 3 Thread 1 Thread2 Thread3 Core1 Core2 Core3

26 Current state of project User application ext3 Virtual Filesystem ne2000 Scheduler cooperative multithreading Memory Flat (up to 512gb) IDE-Disk e1000 Device Driver TORO kernel Hardware (x86-64) Stack TCP-IP Network

27 Thoughts The difference between the kernel and application is becoming more thin. What is the rol of the kernel? When/Why we need a kernel? When we dedicate a kernel, it becomes simpler. TORO represens a compromise between optimization and portability.

28 Questions?

29 Thanks! torokernel.io

Reducing CPU usage of a Toro Appliance

Reducing CPU usage of a Toro Appliance Matias E. Vara Larsen matiasevara@gmail.com Who am I? Electronic Engineer from Universidad Nacional de La Plata, Argentina PhD in Computer Science, Universite NiceSophia