Introduction to Operating Systems and Data Communication

Introduction to Operating Systems and Data Communication

IN2140: Introduction to Operating Systems and Data Communication Operating Systems: Introduction Pål Halvorsen Sunday, 3 February 19 Overview § Basic execution environment – an Intel example (why do you need an operating system (OS), or need to know anything about it) § What is an OS? § OS components and services (extended in later lectures) § Interrupts and system calls § Booting, protection, kernel organization University of Oslo INF2140, Pål Halvorsen Hardware § Central Processing Units (CPUs) § Memory (cache(s), RAM, ROM, Flash, …) § I/O Devices (network cards, disks, CD, keyboard, mouse, …) § Links (interconnects, busses, …) University of Oslo INF2140, Pål Halvorsen An easy, old example: Intel Hub Architecture (850 Chipset) Intel D850MD Motherboard: Source: Intel® Desktop Board D850MD/D850MV Technical Product Specification University of Oslo INF2140, Pål Halvorsen An easy, old example: Intel Hub Architecture i7 motherboard mouse, keyboard, parallel, serial, Intel D850MD Motherboard: network and USB connectors Source: Intel® Desktop Board D850MD/D850MV Technical Product Specification Video PCI Connectors (slots) Memory Controller Hub AGP slot Pentium 4 socket I/O Controller Hub RDRAM PCI interface bus RAMBUS RDRAM – 2 banks (4 slots) Firmware Hub – including BIOS Power connector Speaker Diskette connector Battery IDE drive connectors University of Oslo INF2140, Pål Halvorsen An easy, old example: Intel Hub Architecture application Pentium 4 Processor file system registers cache(s) system bus disk (64-bit, 400/533 MHz !~24-32 Gbps) RDRAM memory RAM interface RDRAM controller (two 64-bit, 200 MHz ! ~24 Gbps) hub RDRAM RDRAM hub interface (four 8-bit, 66 MHz ! 2 Gbps) I/O PCI slots controller PCI slots hub PCI bus (32-bit, 33 MHz PCI slots disk ! 1 Gbps) University of Oslo INF2140, Pål Halvorsen A slightly newer example: Intel Platform Controller Hub Architecture Sandy Bridge, Core i7 Core i7 cache(s registers integrated memory ) Pentiumcontroller 4 Processor iGraphics PCIe registers cache(s) Flexible Display Direct Media Interface (DMI) / Interface (FDI) QuickPath Interconnect (QPI) RDRAM memory Peripherals RDRAM controller hub RDRAM PCH RDRAM Platform Controller Hub I/O PCIePCI slots slots controller PCIePCI slots slots hub PCIePCI slots slots University of Oslo INF2140, Pål Halvorsen Example: IBM POWER 4 application POWER 4 chip Note: communication CPU CPU Again, data touchingfile system operations system L1 L1 add movement operations core interface switch disk network card L2 fabric controller (chip-chip fabric + multi-chip module) RAM file system GX memory L3 controller L3 RAM communication system controller controller RAM application PCI busses GX bus (32/64-bit, 33/66 MHz ! 1-4 Gbps) (two 32-bit, 600 MHz ! ~35 Gbps) network card PCI PCI-PCI PCI slots host bridge bridge remote I/O PCI slots disk (RIO) bridge PCI PCI-PCI host bridge bridge RIO bus (two 8-bit, 500 MHz ! ~7 Gbps) University of Oslo INF2140, Pål Halvorsen Example: IBM POWER 4 POWERPOWER 4 chip 4 chip POWER 4 chip CPU CPU CPU CPU CPU L1 L1 CPU L1 L1 L1 core interface switch L1 core interface switch L2 L2 core interfacefabric controller switch fabric controller RAM RAM GX memory GX memory L3 L3 L3 L3 controller L2 controller controller RAM controller controller controller RAM RAM RAM fabric controller (chip-chip fabric + multi-chip module) RAM GX POWER 4 chip POWER 4 chip memory CPU CPUL3 controller L3 CPU CPU RAM controllerL1 L1 controllerL1 L1 core interface switch core interface switch RAM L2 L2 fabric controller fabric controller RAM RAM GX memory GX memory L3 L3 L3 L3 controller controller controller RAM controller controller controller RAM RAM RAM Multichip modules in fabric controller can connect 4 chips into a 4 chip, 2-way SMP à 8-way MP University of Oslo INF2140, Pål Halvorsen Example: IBM POWER 4 POWER 4 chip POWER 4 chip POWER 4 chip POWER 4 chip CPU CPU CPU CPU CPU CPU CPU CPU L1 L1 L1 L1 L1 L1 L1 L1 core interface switch core interface switch core interface switch core interface switch CPU CPU CPU CPU L1 L1 L1 L1 L2 L2 L2 L2 POWER 4 chip POWER 4 chip fabric controller fabric controller fabric controller fabric controller core interface switch core interface switch RAM RAM RAM RAM GX memory GX memory GX L3 memory GX L3 memory L3 L3 L3 L3 L3 controller RAM L3 controller RAM controller controller controller RAM controller controller controller RAM controller controller controller controller L2 L2 RAM RAM RAM RAM fabric controller fabric controller RAM RAM POWER 4 chip POWER 4 chip POWER 4 chip POWER 4 chip GX memory GX memory L3 L3 L3 L3 controller controller controller RAM CPU CPU controller controller CPU CPU controller RAM CPU CPU CPU CPU L1 L1 L1 L1 L1 L1 L1 L1 core interface switch core interface switch RAM core interface switch core interface switch RAM L2 L2 L2 L2 fabric controller fabric controller fabric controller fabric controller RAM RAM RAM RAM GX memory GX memory GX L3 memory GX L3 memory L3 L3 L3 L3 L3 controller RAM L3 controller RAM controller controller controller RAM controller controller controller RAM controller controller controller controller RAM RAM RAM RAM POWER 4 chip POWER 4 chip POWER 4 chip POWER 4 chip CPU CPU CPU CPU CPU CPU CPU CPU L1 L1 L1 L1 L1 L1 L1 L1 core interface switch core interface switch core interface switch core interface switch CPU CPU CPU CPU L2 L2 L2 L1 L2 L1 L1 L1 POWER 4 chip POWER 4 chip fabric controller fabric controller fabric controller fabric controller core interface switch core interface switch RAM RAM RAM RAM GX memory GX memory GX L3 memory GX L3 memory L3 L3 L3 L3 L3 controller RAM L3 controller RAM controller controller controller RAM controller controller controller RAM controller controller controller controller RAM L2 RAM L2 RAM RAM fabric controller fabric controller RAM RAM POWER 4 chip POWER 4 chip POWER 4 chip POWER 4 chip GX L3 memory CPU CPU GX L3 CPU CPU memory CPU CPU CPU CPU L3 L3 controller controller RAM controller controller RAM L1 L1 L1 L1controller L1 L1 controller L1 L1 core interface switch core interface switch core interface switch core interface switch RAM RAM L2 L2 L2 L2 fabric controller fabric controller fabric controller fabric controller RAM RAM RAM RAM GX memory GX memory GX L3 memory GX L3 memory L3 L3 L3 L3 L3 controller RAM L3 controller RAM controller controller controller RAM controller controller controller RAM controller controller controller controller RAM RAM RAM RAM Chip-chip fabric in fabric controller can connect 4 multi-chips into a 4x4 chip, 2-way SMP à 32-way MP University of Oslo INF2140, Pål Halvorsen Other examples: AMD Opteron & Intel Xeon Intel Xeon MP Processor-based 4P F Different hardware may have different bottlenecks ==> nice to have an operating system to control the HW? University of Oslo INF2140, Pål Halvorsen Different Hardware Application program Application program Operating Application System Operating Application System Hardware X Hardware Y University of Oslo INF2140, Pål Halvorsen Intel 32-bit Architecture (IA32): Basic Execution Environment 16-bit vs. 32-bit vs. 64 bit vs. … ? A big difference between 32-bit processors and 64-bit processors the size/width of the hardware. This affects the amount of data processed per second – the speed at which they can complete tasks. Otherwise, a lot of similarities… … using 32-bit for easier explanations! University of Oslo INF2140, Pål Halvorsen Intel 32-bit Architecture (IA32): Basic Execution Environment § Address space: 1 – 236 (64 GB), each process may have a linear address space of 4 GB (232) § Basic program execution registers: − 8 general purpose registers (data: EAX, EBX, ECX, EDX, address: ESI, EDI, EBP, ESP) − 6 segment registers (CS, DS, SS, ES, FS and GS) GPRs: − 1 flag register (EFLAGS) PUSH %eax EAX: X − 1 instruction pointer register (EIP) PUSH %ebx EBX: Y ECX: EDX: § Stack – a continuous array of memory locations <do something> ESI: − Current stack is referenced by the SS register EDI: − ESP register – stack pointer POP %ebx EBP: POP %eax − EBP register – stack frame base pointer (fixed reference) ESP: see arrow − PUSH – stack grows, add item (ESP decrement) STACK: 0x0... − POP – remove item, stack shrinks (ESP increment) § Several other registers like Control, MMX/FPU (MM/R), Y Memory Type Range Registers (MTRRs), X SSEx (XMM), AVX (YMM), performance monitoring, … ... 0xfff... University of Oslo INF2140, Pål Halvorsen Hidden example with register updates – run yourself… Intel 32-bit Architecture (IA32): Basic Execution Environment code segment: § Example: … 8048314 <main>: main (void) objdump -d 8048314: push %ebp { 8048315: mov %esp,%ebp int a = 4, b = 2, c = 0; 8048317: sub $0x18,%esp c = a + b; 804831a: and $0xfffffff0,%esp } 804831c: mov $0x0,%eax insert value 4 in variable a on stack: 8048322: sub %eax,%esp 0xfffffffc = -(0xffffffff – 0xfffffffc) = -0x4 8048324: movl $0x4,0xfffffffc(%ebp) a’s memory address = EBP - 4 804832b: movl $0x2,0xfffffff8(%ebp) stack: 0x0... 8048332: movl $0x0,0xfffffff4(%ebp) 8048339: mov 0xfffffff8(%ebp),%eax sub 24 (0x18) bytes 804833c: add 0xfffffffc(%ebp),%eax (add space for 24 bytes) 804833f: mov %eax,0xfffffff4(%ebp) 8048342: leave alignment – sub "X" (here 8) bytes 8048343: ret 06 … 2 4 old EBP EAX: EBP: ... Accumulator for operands and results data 602 0xfffffff0??? Pointer to data on stack (base) ... ESP: EPI: ... 0xfff... Stack pointer 0xffffffd80xffffffd00xfffffff40xfffffff0 804832b804831480483158048317804832280483248048332804833980483428048343804831a804831c804833c804833f… Pointer to next instruction to be executed University

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    53 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us