This is the finest video on GOT, PLT topics. Thanks for your efforts.
@KFRogers26313 күн бұрын
Really appreciate the clarification on the server side of the two different fd's. I think that was muddy in my head and now with the diagram and your explaining the difference, it all makes more sense!\
@volovodov15 күн бұрын
> Talks about Linux > Is on Windows mfw
@gemini_53715 күн бұрын
Gemini 1.5 Pro: This lecture is about memory mapping (mmap) and its role in virtual memory. The speaker, Chris Kanich, explains that memory mapping is a technique that allows a process to access a file as if it were directly mapped into its memory address space. This means that the process can read and write to the file using normal memory access instructions, without having to explicitly call read or write system calls. [1,2] One of the benefits of memory mapping is that it can improve the efficiency of memory access. When a process reads from a file using traditional read system calls, the data must be copied from the kernel address space to the user address space. This copying can be time-consuming. With memory mapping, the data is already in the process's address space, so there is no need to copy it. [1,2] Another benefit of memory mapping is that it can simplify the process of sharing memory between processes. Two processes can map the same file into their respective address spaces, and any changes made by one process will be immediately visible to the other. This can be useful for things like shared libraries, which can be mapped into the address space of multiple processes at the same time. [2] The lecture also discusses the concept of copy-on-write (COW). COW is a technique that allows multiple processes to share a read-only page of memory. The first process to write to the page will cause a page fault, and the kernel will create a private copy of the page for the writing process. This means that the original page can still be shared by other processes, and the writing process will not affect them. [2] Overall, memory mapping is a powerful technique that can improve the efficiency of memory access and simplify the process of sharing memory between processes.
@askinc10216 күн бұрын
Great explanation Chris. Keep uploading.
@sheldonhage72620 күн бұрын
I've been doing packet decodes from packet decoders where first introduced (really before Ethernet was invented) and have read and watched seemingly countless examples of tutorials on this subject. This is easily the best one anywhere.
@imane__abas21 күн бұрын
I'm soo in love with your way of teaching this is so unteresting !
@tengjiang8922Ай бұрын
Great lecture! I'm wondering why is spawning subprocesses for ulimit and wc here?
@tengjiang8922Ай бұрын
Thank you. Please keep sharing!
@Fracasse-0x13Ай бұрын
15:00
@AadityaSPatilАй бұрын
This is probably the most in-depth (and clear) explanation of sockets I've seen yet. Thank you very very much.
@erenyeager4452Ай бұрын
Hello, Is the entire playlist here on your channel?
@kblmnАй бұрын
great video.this video clicked the javascript event loop for me.
@kafoby8732Ай бұрын
Thank you for making these lectures FREE!!
@alexkfridgesАй бұрын
I really wish you didnt waffle on about a separate topic for 3 minutes in the middle
@nicolaskeroack7860Ай бұрын
I have few words: crystal clear
@sayansivakumaranАй бұрын
Wanted to add in another thank you for all of your videos. They're really helpful for teaching myself material that I never had the opportunity to take classes for in college :)
@urbankoistinen56882 ай бұрын
It is also worthwhile to test that the system does what the documentation seems to imply it should do. Try mmap on a large file using different flags, see what happens when the file is cashed in main memory.
@DimaLifeIsGood2 ай бұрын
Finally I found a channel that was looking for a long time. Thank you 🙏
@happygofishing2 ай бұрын
Good video
@photopro87642 ай бұрын
Every word of this video is gold! Good job explaining it.
@user-rj8vt9py9i2 ай бұрын
what is the name of the book please ?
@grinlex2 ай бұрын
atomic?
@AmolGautam2 ай бұрын
thanks for this.
@AmolGautam2 ай бұрын
Thanks
@user-jx1go3bf8k2 ай бұрын
Thank you!
@parimi0013 ай бұрын
This is the gold mine I have it. Kudos to the instructor. ❤it
@PUB5T0MP3 ай бұрын
So good.
@louvelpaul22903 ай бұрын
For anyone wondering, he's using the example coming from Computer System: A Programmers Perspective !
@alex_d_lee3 ай бұрын
this is so good
@User-ty2ml3 ай бұрын
Beautiful & Unbelievable, how on earth you made it so simple !!!!
@deez_nu1s4 ай бұрын
nice explanation man, keep up the analogies! <3
@user-ps7eg7zu4d4 ай бұрын
Another way to fix compilation error of multiple definition of `x', one can add `extern` to `int x` in weaklibrary.c. e.g., `extern int x`.
@josiaskas4 ай бұрын
simply the best 👏🏾
@wonderfulworld24754 ай бұрын
When someone on KZbin compress your 4 hour lecture into 20mns :D
@thinkingcitizen4 ай бұрын
chris you are a talented teacher, you should learn all areas of ECE and make lectures for all topics!
@victoriatfarrell4 ай бұрын
Thank you so much for sharing!
@guru.prasath4 ай бұрын
Very good. keep going. Thanks.
@monahf4 ай бұрын
Nicee
@akashagarwal63904 ай бұрын
This is a TCP/ICP socket instead of a Unix Domain socket?
@AnantaAkash.Podder5 ай бұрын
By far the BEST Video
@sharathkumar37285 ай бұрын
Thanks 😊
@bradH20495 ай бұрын
Very well explained. Thank you so much!
@slmjkdbtl5 ай бұрын
bind(), listen() and accept() looks similar, what are the cases they're not used together?
@esteban-alvino5 ай бұрын
Thanks, Im looking for multiplexes, reading about it because my touchpad laptop is not working and seems kernel multiplex is root cause. :D, nice video, way you explain is awesome. Do you post your videos for free or has paid content as well?
@AnantaAkash.Podder5 ай бұрын
By Far the Best Explanation Ever for Socket File Descriptor in UNIX...❤️❤️
@ridhakiller6 ай бұрын
Great video, I really like the analogies it helps a lot !
@trojanhorse82786 ай бұрын
Which book are you referring for all these quality videos?
@adam29334Ай бұрын
Computer Systems, a programmer’s perspective, by Randal E. Bryant and David R. O’Hallaron