跳到主要內容

Install K8S on VM and spring boot integration.

Installation Environment Vmware Workstation pro  It is recommended to use the  snapshot  to store the state of each installation stage to avoid installation failures and causing the installation to start from scratch. Ubuntu 22.04 windows 11 Hardware settings  create 3 VM: 4 cores and 4G memory and 100G capacity Before installing K8s (All use the root user) set host: 192.168.47.135 master 192.168.47.131 node1 192.168.47.132 node2 set root ssh connection: sudo su - echo "PermitRootLogin yes" >> /etc/ssh/sshd_config systemctl restart sshd sudo passwd ssh-keygen for i in {master,node1,node2}; do  ssh-copy-id root@$i; done set Ipvs and conf  create conf file: for i in {master,node1,node2}; do ssh root@$i 'cat << EOF > /etc/modules-load.d/containerd.conf overlay br_netfilter EOF'; done execute conf: for i in {master,node1,node2}; do ssh root@$i 'modprobe overlay;modprobe br_netfilter;'; done create 99-kubernetes-cri.conf file: for i in {maste...

I/O system

I/O hardware

  • Port: a connection point between I/O devices and the host.
    • E.g.: user ports.
  • Bus: a set of wires and a well-defined protocol that specifies messages sent over the wires.
    • E.g.: PCI bus.
  • Controller: a collection of electronics that can operate a port, a bus, or a device.
    • A controller could have its own processor and memory. Etc. (e.g.: SCSI controller).

Basic I/O Method (Port-mapped I/O)

  • Each I/O port (device) is identified by the unique port address.
  • Each I/O port consists of four registers (1~4bytes).
    • Data-in register: read by the host to get input
    • Data-out register: written by the host to send output
    • Status register: read by the host to check I/O status
    • Control register: written by the host to control the device
  • The program interacts with an I/O port through special I/O instructions (different from mem. access).
    • X86: IN, OUT

I/O methods Categorization

  • Depending on how to address a device:
    • Port-mapped I/O.
      • Use different address spaces for memory.
      • Access by special I/O instruction (e.g. IN, OUT).
    • Memory-mapped I/O.
      • Reserve specific memory space for the device.
      • Access by standard data-transfer instruction (e.g. MOV).
      • Good: 
        • More efficient for large memory I/O (e.g. graphic card).
      • Bad:
        • Vulnerable to accident modification error.
  • Depending on how to interact with the device:
    • Poll(busy-waiting): processor periodically checks the status register of a device
    • Interrupt: device notifies the processor of its completion
  • Depending on who controls the transfer:
    • Programmed I/O: transfer controlled by CPU.
    • Direct memory access(DMA) I/O: controlled by a DMA controller (a special purpose controller).
      • Design for large data transfer.
      • Commonly used with memory-mapped I/O and interrupt.

I/O subsystem

  • I/O Scheduling - improve system performance by ordering the jobs in the I/O queue.
    • E.g. disk I/O order scheduling.
  • Buffering - store data in memory while transferring between I/O devices.
    • Speed mismatch between I/O devices.
    • Devices with different data-transfer sizes.
    • Support copy semantics.
  • Caching - fast memory that holds copies of data.
    • Always just a copy.
    • Key to performance.
  • Spooling - holds output for a device.
    • E.g. printing (cannot accept interleaved files).
  • Error handling - when an I/O error happens.
    • E.g. SCSI devices return error information.
  • I/O protection
    • Privilege instructions.

Blocking and Nonblocking I/O

  • Blocking: process suspended until I/O completed
    • Easy to use and understand
    • Insufficient for some needs 
    • Use for synchronous communication & I/O
  • Nonblocking
    • Implemented via multi-threading
    • Returns quickly with the count of bytes read or written
    • Use for asynchronous communication & I/O

Performance

  • I/O is a major in system performance.
  • It places heavy demands on the CPU to execute device driver code.
  • The resulting context switches stress the CPU and its hardware caches.
  • I/O loads down the memory bus during data copy between controllers and physical memory.
  • Interrupt handling is a relatively expensive task.
    • Busy waiting could be more efficient than interrupt-driven if I/O time is small.

Improving performance

  • Reduce the number of context switches
  • Reduce data copying
  • Reduce interrupts by using large transfers, smart controllers, polling
  • Use DMA
  • Balance CPU, memory, bus, and I/O performance for highest throughput
reference:
https://www.amazon.com/-/zh_TW/Operating-System-Concepts-Abraham-Silberschatz/dp/1119800366/ref=sr_1_1?keywords=Operating-System-Concepts&qid=1669538704&s=books&sr=1-1

留言

這個網誌中的熱門文章

Install K8S on VM and spring boot integration.

Installation Environment Vmware Workstation pro  It is recommended to use the  snapshot  to store the state of each installation stage to avoid installation failures and causing the installation to start from scratch. Ubuntu 22.04 windows 11 Hardware settings  create 3 VM: 4 cores and 4G memory and 100G capacity Before installing K8s (All use the root user) set host: 192.168.47.135 master 192.168.47.131 node1 192.168.47.132 node2 set root ssh connection: sudo su - echo "PermitRootLogin yes" >> /etc/ssh/sshd_config systemctl restart sshd sudo passwd ssh-keygen for i in {master,node1,node2}; do  ssh-copy-id root@$i; done set Ipvs and conf  create conf file: for i in {master,node1,node2}; do ssh root@$i 'cat << EOF > /etc/modules-load.d/containerd.conf overlay br_netfilter EOF'; done execute conf: for i in {master,node1,node2}; do ssh root@$i 'modprobe overlay;modprobe br_netfilter;'; done create 99-kubernetes-cri.conf file: for i in {maste...

SOLID

SOLID is the fundamental and core principle of OOP. Single-Responsibility Principle High cohesion: A module preferably has only one business logic. Low coupling:   The different modules work independently and are connected by simple protocols to minimize side effects. Open-Closed Principle Open for extension:  It is easy to extend new functions with existing code. Close for modification:  Do not modify existing classes to ensure stable functions. Liskov-Substitution Principle A superclass should be replaceable with objects of its subclasses without breaking the application. Interface-Segregation Principle Clients only depend on the interfaces they need, don't use the "big" interface to contain everything. Dependence-Inversion Principle The program should depend upon abstractions, not concretions. reference: https://en.wikipedia.org/wiki/SOLID https://blog.knoldus.com/what-is-liskov-substitution-principle-lsp-with-real-world-examples/ https://github.com/hollischuang/toBeTo...

Cpu scheduling

Table of contents [ hide ] Basic concept The idea of multiprogramming: Keep several processes in memory. Every time one process has to wait, another process takes over the use of the CPU. CPU-I/O burst cycle: Process execution consists of a cycle of CPU execution and I/O wait(i.e., CPU burst and I/O burst). Generally, there is a large number of short CPU bursts and a small number of long CPU bursts An I/O-bound program would typically have many very short CPU bursts. A CPU-bound program might have a few long CPU bursts. CPU scheduler Select from the ready queue to execute(I.e allocates an APU for the selected process) CPU scheduling  decision may take place when a process: Switch from running to waiting state. Switch from running to ready state. Switch from waiting to ready. Terminates. Non-preemptive scheduling: Scheduling under 1 and 4(no choice in terms of scheduling). The process keeps the CPU until it is terminated or switched to the waiting state. Preemptive schedul...