Please enable JavaScript.

Coggle requires JavaScript to display documents.

Linux Kernel Source code https://elixir.bootlin.com/linux/v6.16/source -…

- - - - 4GB
        
        Assigned to a process
      - 4GB
        
        Assigned to a process
        
        Dynamic space?
        
        When a process is created, ithas its memory distribute in these elements.
        
        Global variables is a bad habit?
        They're located in sata, just above the text, they will never disappear.
        
        Colateral effects
        
        Attribute are local for the class
        
        Aked to ChatGpt:
        https://chatgpt.com/share/6898af9d-6164-800a-b779-0c0d8679c818
        
        Colateral effects
        
        Not working properly neither parameters or data structures.
        If a function requires a data to program, you have to add it as a parameter. If you do not add it, then you can use a global variable.
        Between many entities or instances of functions and procedings, they're sharing the variable and can have catastrofic results.
        
        With global variables, you're not doing an appropiate usage of parameters and data structures
        
        When main is called, in the stack is assigned a space for the function where it ios first added its parameter.
        Stack will be growing according to the function extent.
        
        Next other function, more space in the stack (context)
      - 4GB
        
        free
      - 4GB
        
        free
    - - What will happen if the program doesn't occupy that sapce (ex 4GB), can it be assigned to other process iwhen opened?
  - - - due to
        
        growth
        
        compiling, traspasses to the memory
  - - - How many processes it has.
      - Description of the processes
- - - - STATES
        
        new
        
        the object exists.
        
        running
        
        In the execution process.
        
        waiting
        
        The process asks for I/O device and then it has to wait.
        
        list, not FIFO. since it's not in order, you can't predict that much.
        
        terminated
        
        Take out of the queue but nothing is pendant
        Closing an app with finished tasks, we can leave or system in a incosistent task.
        
        ready
        
        The object forms a part of the queue (FIFO)
        
        The names can change accorsing to the program
        
        Just for comprehension: We consider only one process executing and the rest are waiting in the queue.
        Notify with an interruption.
    - - parent's processes
      - children and siblings
      - memory info
  - - - However, C doesn't have 'preceding' but it is a structure language.
        However, there is a way to add 'procedimientos en C'
      - When we order the code in function and proceding, we pass parameters the data that the functions need to work.
      - 2 big dont's
        
        Structured Language
        
        Structure language shouldn't allow global variables.
        Having many instances and classes is sharing and can have catastrophic results.
        
        Coupling
        
        How much a program depends on another
        
        why?
        Code that is easy to reason about, test, change and reuse.
- - - - Reference to the real directions of the system
- - - - When it finishes, they have to give you back a result.
- - - - https://medium.com/@mukulagrawaly2k/cpu-scheduling-algorithms-visualiser-9dcc0ca76b54
- - - - zombie process:
        A zombie process is a child process that has already finished running but still has a tiny entry in the OS’s process table because its parent hasn’t collected its exit status yet. It’s “dead” code-wise, but not fully cleaned up.
      - output shows lots of sleeping tasks because most desktop processes spend time blocked on input/events. Sleeping means 'blobked' or waiting for an event.
        
        To read in more detail what you see in top
        https://www.notion.so/What-you-see-in-Top-24b932afb72480ef8a16c43005336d60