Operating Systems 2017F Lecture 19

[Notes]

Sample sample

Additional Notes

Where's main?

• lots of program shave "main" functions - a function that runs first and controls the execution of the program
  
• Do these have "main" functions?
  
  • Linux kernel modules
    
  • FUSE applications?
    
  • the linux kernel?
    
  • node web applications?
    

In many systems, "main" just sets up even handlers

• the event loop can be implicit or explicit
  
  • or there may be no loop at all, just handlers and "interrupts" some kind
    
• event loops poll (check) to see when there are new events
  
• what are event loops for node app?
  
  • where are interrupts for node apps?
    
    • Incoming network requests, it's an event
      

Code run differently in the kernel :

1)functions runs on the bhealf of insmod, unles sit is Independence context

2)codes that run on the bhelaf o the process

3)after an interrupt: no process , it is an interrupt cotext

4) file names : regular programs but the square brackets, execution context + address space. they share the kernel's address space, they are called kernel threads which are independently scheduling . You can not kill them but you can change their scheduling , maybe their priority but not 100%.

does it create a proces? no , but it can create a kernel thread (is it a process? virtual adress space, .
multi- threaded: maintains multiple address processes , ex: fire fox.

ps -elF | less "number" : displays threads.

top : displays all the processes

ls time : shows you the time .

sys: how much time in the kernel space real: how much time user : how much time in user space

process : can't manipulate its own memory map directly, it has an address space, but cant change it. Process: is limited but the kernel is not and the kernel can change it's own address and in charge of its self.

Kernel tasks : are threads, when a process makes a system call , thi sis schedules in the process priority.

When running
"time ls"
real = realtime it took to run user = the user space time sys = kernel time

What's flow of control in tutorial 7?
What is the connection?
To exit the program, we must unmount the filesystem, run "sudo umount mnt"

OS kernels are essentially the same thing

what is the flow of control ? what connection between things we are doing in the new terminal and the old one

-> these programs are communicating to each other, it will be invoked when we use mnt (mount) the kernel knows it is a filesystem , process runs system calls, then kernel talks to out original terminal. How? you can use strace to know, it is waiting to be invoked, to receive and responds to messages. events will be passed off to another process. switching between one process to another. it has potential security benefits.

Key to understand this tutorial :

-> understand net flow control.

-> how do processes communicate?

-> how does it take a directory int and creates a filesystem from it?:

• • • sub tree starting at mount is delegated to this process.
      
    • permissions are limited
      

How to kill it?

-> ctrl c , no , you can but the kernel will be unhappy.
-> unmount the file system when you are done using it
-> umount / you have to do it as root

Node web applications

• Theres not a dedicated main function but its the first thing that runs
  
• Every line in the node application terminates
  
• If you start a web server, the function call starting it will terminate
  
• Whats running? The main has finished. Is the program doing anything actively if theres no external input?
  
• In many systems main just sets up event handlers
  
• The event loop can be implicit or explicit
  
• Its possible to have no loop at all just handlers and interrupts of some kind
  
• Event loops check to see when there are new events
  
• Os kernels behave the same way as node applications
  
• Waiting for events
  

What happens when you use insmod?

• In newgetpid: Init and exit are called when the insmod program makes system calls to load the module
  
• Init is run on behalf on insmod
  
• Kernel code fits into 3 categories
  
  • Code that runs on behalf of a process
    
  • Code that runs after an interrupt
    
  • Kernel threads, has lots of functionality
    

Why is a kernel thread not a process?

• The kernel maintains its own address space
  
• Has its own virtual address map
  
• The kernel always has just 1 address space regardless of how many threads there are
  
• Processes cannot manipulate its own memory map directly, needs to ask kernel first
  
• Processes are limited, the kernel is not, has control over itself
  

• Kernel tasks = kernel threads
  
• Independently scheduled
  
• Once we call insmod everything happens in user space
  
• Strace uses a system call called ptrace
  

Tutorial 7: Fuse

• Memoryll.py program
  
• Always unmount a filesystem when youre done using it
  

• No class Thursday! no office hours on Wednesday