I'm not sure that symlink example is all right. Symlink is just a special kind of file that just contains a path. It does not points directly to the inode, that would be a hardlink, which you can't create between different file systems. With symlink, I believe, it should go back to the begining, just with a new filepath to find.
100% True. I simplified my schematics without mentioning it in the vid, Thanks for pointing it out! For thoses watching, here is what the full image should look like: imgur.com/a/LgVPj2D
This is an excellent video, and it also shows how impressive the Linux kernel is as a free and open-source software. However, a question that stuck with me is how much memory that inode list uses and how the kernel determines the size limit for caches in general.
I don't think that there is a Max size for the cache. There is the vfs_cache_pressure that will determine when to remove entries from the cache. There are 2 things to remember with vfs cache, 1. Those entries are really small (I don't have the specific size, but it is for sure not over 300 bytes), and linux will never clear cache unless memory is requested by another process. Unused memory is a wasted memory!
I'm not sure that symlink example is all right. Symlink is just a special kind of file that just contains a path. It does not points directly to the inode, that would be a hardlink, which you can't create between different file systems. With symlink, I believe, it should go back to the begining, just with a new filepath to find.
100% True. I simplified my schematics without mentioning it in the vid, Thanks for pointing it out!
For thoses watching, here is what the full image should look like: imgur.com/a/LgVPj2D
Great Work, really appreciate you sharing your notes. Hope your channel continues to grow
Wow! Big thanks for the dono!
Great work again!!, excited for linux 6.12 video
6.12 is insane! The hype is real!
Great video, love the mario example lol. Didn't know about the mkfifo command.
Fun fact: Unix was the first operating system to treat files as streams of bytes and abstract physical and logical records
Really interesting!
Wonderful video. Can you make, or suggest, a video on Windows IFS and how it differs from VFS.
There are some ext4 and btrfs IFS drivers
Will look into it!
@@Maple-Circuit thanks! While Microsoft is proprietary they do have extensive documentation these days.
Waiting for this
This is an excellent video, and it also shows how impressive the Linux kernel is as a free and open-source software. However, a question that stuck with me is how much memory that inode list uses and how the kernel determines the size limit for caches in general.
I don't think that there is a Max size for the cache. There is the vfs_cache_pressure that will determine when to remove entries from the cache. There are 2 things to remember with vfs cache, 1. Those entries are really small (I don't have the specific size, but it is for sure not over 300 bytes), and linux will never clear cache unless memory is requested by another process. Unused memory is a wasted memory!
what did you use to make those diagrams?
This looks like an obsidian canvas document with a modified theme. Hope this helps.
Obsidian with advanced canvas.
Lesgoo
Please continue
Ain't stoppin nooowwww
Thanks :3
Too many things are abstracted by the operating system!
Feel free!!