Holy crap. UKposts algorithm finally came through. This is some amazing content.

Hey if you are seeing this, let me tell you, this is the best video in UKposts if you want to understand the concept of virtual memory, and others in simple and sweet. Perfect! ❤

This is amazing! More detail than most Operating System courses in 20 minutes. Awestruck!

Fantastic video. I'm taking a OS course at university and we have a virtual memory assignment. The hand out documents left me feeling confused and a bit lost, but then this 20-minute video made all concepts clear as day. Thank you for putting effort into making these videoes, you earned a new subscriber!

Thank you for the video. The explanation was clear, structured and concise, better than most other explanations on youtube.

I had a course back when i was in engineering school, the professor did a horrible job explaining memory and virtual memory, I ended up hating the class and i never really understood how it worked. until this day when I watched your video, you did an excellent job, I wish youtube had something like this before. Fast forward today, I work as a sysadmin/infra engineer and i really didn't have an idea how virtual memory works, again until I watched your video, thank you for the effort you put here, I am sure many will watch it and gain valuable informations.

This might be the best content I have found on UKposts this year. You explained these concepts in ways my teachers couldn’t, and you did it for free too ! You have my respect , and subscription haha !

There's a quite good reason 4 KB is used as a standard page size. In most disk partitioning software the minimum data you can read/write to is 4KB, so it can move it in one swoop

I wanna thank the youtube algorithm for recommending this video. This is absolute gem for explaining the Virtual Memory concept.

Amazing explanation, always wanted to know core knowledge. Thanks, keep up with these videos!

Excellent description on how cpu/memory/os are working together! Well done!

This video is really good, the way that you simplified Virtual Memory is amazing!

Dude, you're videos are so helpful, thanks so much!!!

That's a very good, high quality production with a top notch explanation! Keep making more.

Thanks! You explained this better than any professor did when I was still in university. Much appreciated, will be sending this video to people who ask me about this 😅

Wow! Clear, concise and very neat animations! Subscribing to a channel after a long time!

Wonderful illustration of Virtual Memory. Good Job !

Great video ! I am preparing for my master degree and found this gold in UKposts. I believe I can ace my upcoming OS class. I have liked your video and subscribed to your channel. Thanks a lot for the video. Greatly appreciate it.

I have to words! That video is amazing! You won yourself a new subscriber, my friend! ❤

Your explanations are amazing Thank you, I hope to see more

Im just sitting here fascinated...and it makes sense.. knowing just the basics... nice work...a dumb thing to say but this is relaxing...straight to the point ..ask a question ...then answer it... terrific

This is awesome, made things so clear to me. Thank you.

the graphics really helped me visualize how this works! youre a lifesaver ^^

please never stop, really good video

Thank god I found this gem before my exam!

What an excellent overview. Nice job. It clarified a few things i was unclear about.

Wow, good video. Good job and thanks for sharing.

An excellent, succint and illustrative explanation :)

Svaka cast burazeru. Ovo sam na faksu radio, ali si dosta bolje objasnio.

شكرا thanks 👍 it was helpful

Wooow this video is awesome! Great work on the animations and examples 🤝😎

From Aritmetic concepts , the virtual memóry obeys bijective function (injective and surjective ) about Domain and Image . It is unbelievable !

Very clear! It helps a lot, thank you very much!😀

Superb...! Love it..❤

Very helpful ❤❤

nice video bro!

Oh Juniors, 1GB is huuuuge for old-school guys

thank you, this video was very clarifying.

watched the first video in this channel, subbed!

bro you are amazing, love your energy

such a good video, you are the man !

Can u make a video for registers, What are they used for… in a way that we can understand the assembly language

This is a very good, concise and clear explanation, please keep the work's up, I really enjoyed it : ) PS: can you make a video about how compression algorithms work?

Well explained

Thank you for providing such valuable content. The examples you shared have greatly enhanced my understanding of the working principles of virtual memory.

clear as water, thanks!

Hey man, can you make same video with gpu and cpu? Your explanation is so good

Truly amazing

Very well explained

I like this video, shows the more "technical side" of virtual memory and how it does its thing. Thanks.

Liked, subbed, turned on all notifications.

Bravo !

Starting off with the “bad old days” only being 4GB definitely lets me know I’m old! Just like running out of 32bit address space “must” have been back in the 1950s or something 😂

great video. i didnt get 2^32 adreess for each byte = 2 ^ 30 words

Thank a lot.

thank you man

Greate Video. Thanks

Great video. So you mention that physical address is the "memory RAM". You also mention the "page tables" are store in the "memory RAM" and how there are difference level of page tables and some can be store in disk. Is virtual memory also store in the "memory RAM"?. I know I have to rewatch this video and keep studying to fully understand and that I have gaps in my knowledge. So in a high level the OS has to do a mapping between virtual memory and page tables. And then between page tables and physical address? Thanks.

I'm already at about 10 minutes and have about 80% understanding. What do you recommend I look for? Or if you have some resource/s I would be grateful

8:06 Correction: A word is two bytes in size, not 4. A double word (DWORD) is 4 bytes. And cpu's don't work with words necessarily, but general purpose registers of x32 bit cpu's are 32 bits in size. And 64 bits for x64 gprs.

Perfect. you did great job here, this topic became very easy after that sweet explanation but I need u to correct my info if I am wrong! in old days we know that byte is 8 bits word is 2 bytes = 16 bits dword is double words = 4 bytes = 32 bits so, is it changed those days as you claim in this video here 8:08 !!! is word become 32-bits ? thank you

Is Page Table update and TLB update treated as 1 atomic operation? If yes, how do we maintain atomicity? If no, how do we handle scenarios where the TLB has stale entry?

you are a legend

Your channel is a masterpiece! The Discord link is invalid or expired. Would you please comment it here? Thank you

UKposts suggesting me at 2 am here. thank god it did. I can sleep well now.

@0:54 and before that there were 16 bit CPUs that could only address which was only 64 Kilobytes. In the early days it was more around the problem with memory collisions rather then accessing something that is out of range. In the 1960s you wouldn't find the kind of problem you're talking about because the processing power was too expensive to have that kind of problem. Paper Tape and Punch Cards don't have the same problems with accessing memory out of range.

Can you next teach us about deditated WAM?

Quite good video. Just a minor comment. You use the word 'Security' in sections but I would call it 'Liability'. Thanks,.

Finally ... a proper explanation! I say this because countless self-made experts get it wrong. You see, Microsoft seems to have invented the misuse of the term "virtual memory" around the time of Windows 95. They used the term VM to describe what is really demand paging. Microsoft publications at the time did NOT make this mistake. (See Jeff Richter's excellent book describing the internals of Windows NT, published at the time.) But in the settings UI ... I guess "virtual memory" sounded more appealing to Microsoft than "demand paging". So they misused the term ... and misled generations of self-made CS people who subsequently grew up unaware of the misuse. They often claim that VM size can be adjusted. (It cannot be.) They believe that the disk swap/paging space is virtual memory. (It is not.) You see, virtual memory was created as a MAPPING PROCEDURE that solved the long-standing problem of mapping a program binary into the run-time address space of a computer. It was preceded by address space paging (remember the early 80x86 paging registers?). This was present in minicomputers as far back as the late 1960s. Paged memory was, in turn, preceded by run-time relocation ... a tedious run-time editing of a binary to "patch" all of the code addresses and data addresses within a program binary before execution could begin. VM is superior to both of those methods. Meanwhile some systems implemented something called swapping ... a predecessor of demand paging. When swapping, a program's ENTIRE memory consumption is swapped to disk to make way for another program. This mechanism allows the system to get around memory size limitations ... but it performs a lot of disk swapping! Demand paging goes one better by swapping only small blocks of memory. And even better, it loads only portions of a program when needed. No need to load an entire program when most of that program code won't be executed any time soon. It's all quite efficient. Virtual memory is not demand paging, and demand paging is not virtual memory. And you don't have to use VM with demand paging. And you don't have to use demand paging with VM. But the two appeared at a similar time in computing history ... and they work hand in hand to improve performance. So you always see both of them together. This video correctly presents a unified view of demand paged/virtual memory. Nice work!

is there a chance that a virtual page does not map to eithjer the disk or the physical page? what happens in that case? 12:45

11:38 I’m wondering when you copy the last 12bits to the physical memory, why the number changes from 0110 0111 1000 to 010110011110

subbed.

Me traga mais sugestões assim de canal algoritmo do UKposts, very good

Very good

Can you recommend some books that deep dive into how Linux works with CPU, memory and disc access

does page table also handle swap, putting memory onto hard disk?

0:35 As far as I understand, 4Gb of memory means less than 4Gb of RAM. CPU thinks that ROM and south bridge devices are memory as well.

Kindly make part 2 for DP

10:39 All pages are 4096 long except Pages 2, is that a correct?

@12:17 He says cpu does not know how to read it from RAM should not it be Disk ?

❤

Subscribed immediately 👍🏾🫡… thank you sir

amazing

amazing. u say program. is this referring to a process?

1:00 Wouldn't the memory address wrap around and not crash immediately?

how to make this animation?

Commenting for the algorithm 😅

Is TLB same as cache ?

great

where are you from? just for the accent. (English learner)

Isn’t a word 16bits and a dword 32?

Discord link is invalid

Good meme video was enjoyable. I must be getting too old for kids to be shitposting in a shitpostable thread.

4:50 The virtual memory system doesn't know that it is on disk, it just knows that it is inaccessable to the program.

W

DMA

so virtual memory is not virtual memory. got it :)

"Programs used to crash in the 1950s or so"? Calm down, it hasn't been that long since Windows XP would ask you to "send an error report".

You had 32 bit CPUs in the 1950's? wtf is this lol.