Operating systems cmpsc 473
Download
1 / 52

Operating Systems CMPSC 473 - PowerPoint PPT Presentation


  • 92 Views
  • Uploaded on

Operating Systems CMPSC 473. I/O Management (3) December 07, 2010 - Lecture 24 Instructor: Bhuvan Urgaonkar. File System. Read Sectors. Write Sectors. Block Interface. Controller (FTL). RAM. Flash Memory. Flash Solid State Drive (SSD). Basics of NAND Flash Memory. Data. OOB. Page.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Operating Systems CMPSC 473' - yetta-leon


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Operating systems cmpsc 473

Operating SystemsCMPSC 473

I/O Management (3)

December 07, 2010 - Lecture 24

Instructor: Bhuvan Urgaonkar


Flash solid state drive ssd

File System

Read Sectors

Write Sectors

Block Interface

Controller

(FTL)

RAM

Flash Memory

Flash Solid State Drive (SSD)


Basics of nand flash memory
Basics of NAND Flash Memory

Data

OOB

Page

Page

Page

Page

……

Page

Data

OOB

Data

OOB

Data

OOB

Page

Page

Page

Page

Page

Page

……

……

……

……

Page

Page

Page

NAND Flash

Block

Block

Block

  • Three operations: read, write, erase

  • Reads and writes are done at the granularity of a page (2KB or 4KB)

  • Erases are done at the granularity of a block

    • Block: A collection of physically contiguous pages (64 or 128)

    • Block erase is the slowest operation requiring about 2ms

  • Writes can only be done on erased pages


Out of place updates
Out-of-Place Updates

Update

Data

LPN=A, V

LPN=A, V

Free

Invalid

LPN=B, V

LPN=C, V

OOB

LPN

PPN (PBN, Offset)

(0, 3)

A

A

(0, 0)

B

(0, 1)

C

(0, 2)

Flash Mapping Table

Block 0

  • Over-writes on the same location (page) are expensive

  • Updates are written to a free page

  • OOB area

    • Keeps valid/free/invalid status

    • Stores LPN, used to reconstruct mapping table upon power failure


Garbage collection
Garbage Collection

  • Reclaims invalid pages

  • Typically, called when free space falls below a threshold

  • Victim block selection

    • Small # valid pages (reduce copying overhead)

    • Small # overall erases (wear level)

5


Flash translation layer ftl
Flash Translation Layer (FTL)

  • Flash Translation Layer

    • Emulates a normal block device interface

    • Hides the presence of erase operation/erase-before-write

    • Address translation, garbage collection, and wear-leveling

  • Address Translation

    • Mapping table present in small RAM within the flash device



Cost

  • Main memory is much more expensive than disk storage

  • The cost per megabyte of hard disk storage is competitive with magnetic tape if only one tape is used per drive.

  • The cheapest tape drives and the cheapest disk drives have had about the same storage capacity over the years.

  • Tertiary storage gives a cost savings only when the number of cartridges is considerably larger than the number of drives.



CPU/Memory

Sub-system


Disk scheduling
Disk Scheduling

  • Ordering of requests issued to disk

    • In OS: Device driver: order requests sent to controller

    • In controller: order requests executed by disk arm

  • Typical goal: Minimize seek time (our focus)

    • Seek time dependent on seek distance

  • More advanced

    • Incorporate rotational latency as well

    • Incorporate notions of fairness


Disk scheduling cont
Disk Scheduling (Cont.)

  • Several algorithms exist to schedule servicing of disk I/O requests.

  • We illustrate them with a request queue (0-199).

    98, 183, 37, 122, 14, 124, 65, 67

    Head pointer 53


FCFS

Illustration shows total head movement of 640 cylinders.


SSTF

  • Selects the request with the minimum seek time from the current head position.

  • SSTF scheduling is a form of SJF scheduling; may cause starvation of some requests.

  • Illustration shows total head movement of 236 cylinders.



SCAN

  • The disk arm starts at one end of the disk, and moves toward the other end, servicing requests until it gets to the other end of the disk, where the head movement is reversed and servicing continues.

  • Sometimes called the elevator algorithm.

  • Illustration shows total head movement of 208 cylinders.



C scan
C-SCAN

  • Provides a more uniform wait time than SCAN.

  • The head moves from one end of the disk to the other. servicing requests as it goes. When it reaches the other end, however, it immediately returns to the beginning of the disk, without servicing any requests on the return trip.

  • Treats the cylinders as a circular list that wraps around from the last cylinder to the first one.



C look
C-LOOK

  • Version of C-SCAN

  • Arm only goes as far as the last request in each direction, then reverses direction immediately, without first going all the way to the end of the disk.



File system structure
File-System Structure

  • File structure

    • Logical storage unit

    • Collection of related information

  • File system resides on secondary storage (disks)

  • File system organized into layers

  • File control block – storage structure consisting of information about a file




In memory fs structures
In-Memory FS Structures

  • Opening a file

  • Reading a file


File system structure1
File-System Structure

  • File structure

    • Logical storage unit

    • Collection of related information

  • File system resides on secondary storage (disks)

  • File system organized into layers

  • File control block – storage structure consisting of information about a file


Virtual file systems
Virtual File Systems

  • Virtual File Systems (VFS) provide an object-oriented way of implementing file systems.

  • VFS allows the same system call interface (the API) to be used for different types of file systems.

  • The API is to the VFS interface, rather than any specific type of file system.



Directory implementation
Directory Implementation

  • Linear list of file names with pointer to the data blocks.

    • simple to program

    • time-consuming to execute

  • Hash Table – linear list with hash data structure.

    • decreases directory search time

    • collisions – situations where two file names hash to the same location

    • fixed size


Allocation methods
Allocation Methods

  • An allocation method refers to how disk blocks are allocated for files:

  • Contiguous allocation

  • Linked allocation

  • Indexed allocation


Contiguous allocation
Contiguous Allocation

  • Each file occupies a set of contiguous blocks on the disk

  • Simple – only starting location (block #) and length (number of blocks) are required

  • Wasteful of space (dynamic storage-allocation problem)

  • Files cannot grow



Linked allocation

pointer

block =

Linked Allocation

  • Each file is a linked list of disk blocks: blocks may be scattered anywhere on the disk.


Linked allocation cont
Linked Allocation (Cont.)

  • Simple – need only starting address

  • Free-space management system – no waste of space

  • Mapping

Q

LA/508

R

Block to be accessed is the Qth block in the linked chain of blocks representing the file.

Displacement into block = R + 4

File-allocation table (FAT) – disk-space allocation used by MS-DOS and OS/2.




Indexed allocation
Indexed Allocation

  • Brings all pointers together into the index block.

  • Logical view:

index table



Indexed allocation cont
Indexed Allocation (Cont.)

  • Need index table

  • Random access

  • Dynamic access without external fragmentation, but have overhead of index block.

  • Mapping from logical to physical in a file of maximum size of 256K words and block size of 512 words. We need only 1 block for index table.

Q

LA/512

R

Q = displacement into index table

R = displacement into block


Indexed allocation mapping cont
Indexed Allocation – Mapping (Cont.)

  • Mapping from logical to physical in a file of unbounded length (block size of 512 words).

  • Linked scheme – Link blocks of index table (no limit on size).

Q1

LA / (512 x 508)

R1

Q1= block of index table

R1is used as follows:

Q2

R1 / 512

R2

Q2 = displacement into block of index table

R2 displacement into block of file:


Indexed allocation mapping cont1
Indexed Allocation – Mapping (Cont.)

  • Two-level index (maximum file size is 5123)

Q1

LA / (512 x 512)

R1

Q1 = displacement into outer-index

R1 is used as follows:

Q2

R1 / 512

R2

Q2 = displacement into block of index table

R2 displacement into block of file


Indexed allocation mapping cont2
Indexed Allocation – Mapping (Cont.)

outer-index

file

index table



Free space management
Free-Space Management

  • Bit vector (n blocks)

0

1

2

n-1

0  block[i] free

1  block[i] occupied

bit[i] =



Block number calculation

(number of bits per word) *

(number of 0-value words) +

offset of first 1 bit


Free space management cont
Free-Space Management (Cont.)

  • Bit map requires extra space

    • Example:

      block size = 212 bytes

      disk size = 230 bytes (1 gigabyte)

      n = 230/212 = 218 bits (or 32K bytes)

  • Easy to get contiguous files

  • Linked list (free list)

    • Cannot get contiguous space easily

    • No waste of space



Efficiency and performance
Efficiency and Performance

  • Efficiency dependent on:

    • disk allocation and directory algorithms

    • types of data kept in file’s directory entry

  • Performance

    • disk cache – separate section of main memory for frequently used blocks

    • free-behind and read-ahead – techniques to optimize sequential access

    • improve PC performance by dedicating section of memory as virtual disk, or RAM disk


Page cache
Page Cache

  • A page cache caches pages rather than disk blocks using virtual memory techniques

  • Memory-mapped I/O uses a page cache

  • Routine I/O through the file system uses the buffer (disk) cache

  • This leads to the following figure



Unified buffer cache
Unified Buffer Cache

  • A unified buffer cache uses the same page cache to cache both memory-mapped pages and ordinary file system I/O



ad