Save this video free

ECE344 Fall 2026 (Sec 1) Lec 22 - Disks

Jon Eyolfson · 49:05 · Watch on YouTube

Part of University of Toronto ECE 344. See all 22 lectures and search them

These notes were made with YouTube Collector. Paste any YouTube link and get the same: a summary, chapters and a searchable transcript.

Overview

Jon Eyolfson explains how operating systems move disk blocks through caches, device drivers, shared request queues, DMA, and interrupts, including how xv6 uses paravirtualized virtio devices. He then compares NAND SSD constraints and RAID layouts, showing how RAID 0, 1, 5, 6, and 10 trade capacity and performance against tolerance for disk failures.

Key takeaways

Chapters

0:00 Disk Blocks, Sectors, and Linux Device Files
7:52 Buffer Caches, DMA, and Disk-Completion Interrupts
16:09 How xv6 Uses Paravirtualized virtio Disks
19:19 NAND SSD Pages, Erase Blocks, and TRIM
25:39 RAID 0 Striping Versus RAID 1 Mirroring
30:44 XOR Parity in RAID 4 and RAID 5
38:14 RAID 5 Failure Risks and RAID 6 Dual Parity
41:14 Nested RAID Layouts and the RAID 10 Tradeoff
47:31 Disk-System Recap: Queues, TRIM, and RAID Choices

Keep these chapters and the full searchable transcript in your own library.

Transcript excerpt

2:39 Oops. >> All righty. We are on our last topic now. So, at the beginning, we had three major concepts, virtualization, which we've well, we haven't quite beat to death, but we've used a lot. And second one was concurrency, and the third one was persistence. So, we get to start talking about persistence today and start talking about disks. So, going back to test one, a process blocking and read uses no CPU. Test one, remember I asked that to you? Yeah, the kernel puts it to sleep, runs something else. It isn't runnable, so the scheduler would completely skip over

3:27 it. So, how does exactly does the kernel know that data is there and wake it up right away? So, today we get to talk about how the kernel actually talks to the disk at a high level, and then what's inside the disk and how to use a lot of them. So, a disk is something called a block device. So, lecture two, everything I told you everything gets represented as a file. So, on Linux at least and also Mac OS, there's this dash dev, and you can there's a whole bunch of names. If If NVMe zero whatever on my machine, that's my whole disk represented as one file. So devices are all files in this dash dev and come in two kinds. There's a character device, which is a stream of

4:15 bytes in order. So your terminal is an example of a terminal or as a character device or dev null that just produces a whole bunch of zero bytes. And then a block device stores fixed size blocks. So just what's the fixed size blocks? How big are they? Depends on the device, but they operate in blocks. Each block gets assigned a number.

This is the start of the transcript. Save this video free for the whole transcript, searchable and time-coded.

In this course

Related notes

Summary, takeaways, and chapters were generated by AI from the video's transcript and may contain errors. The video belongs to its creator, Jon Eyolfson.

Want the full transcript?

Save this video in YouTube Collector to get its complete searchable transcript, your own AI summaries, and a library that keeps every video you collect in one place.