I love your videos. This is such a great digest for Kernel Updates. I learned about so many things about the kernel that I probably would have never heard of. This is truly a hidden gem that more people in the community need to see.
Thanks you for that series of videos! I particularly like your 6.10 and 6.11 part 1 videos because you explained all the abbreviation and kernel subsystems, so mere mortals (though still familiar with system programming a bit) people can understand the changes and kernel slang. In 6.11 part 2 it feels like you try to cover all the changes for the cost of explanation. It is still good video, but I would like to point that the value (for me) of your videos in exactly these explanations and not in the news itself. And relly looking forward for your next videos to know a bit more about kernel and modern system programming! Thank you!
Okay, It looks like lack of explanation and amount of abbreviations was related to VM section. Once video get to Memory section you are back on track with explanations! :)
You are right! I really tried to fit everything that happened on this release. Next time, I'll probably cut some of it out so we can get more explaining, which is really the best part of the videos (;
6:40 my guess is it was never an issue due to how crts worked. tho it did take a few decades for VRR to be a common feature. maybe more so for power efficiency
Writing a kernel from scratch would look like a much sounder approach, there's already one in Rust, why don't they focus on this instead of trying to "invade" Linux (I know why: money)? As to languages, Rust is certainly not what I would have picked for a new kernel, if I wanted to try something else than C.
What is a navy gpu? Also funny how the iris xe driver is worse than the i915 driver, but they are making an xe2 driver before the previous one is even working well.
You are doing a great job with this summary. It's very instructive, nicely explained, not boring. This must be quite a lot of work. Very nice. Thank you!
@@Maple-Circuit I think we get the better end of the deal here. Big thanks! You seem to have an in depth understanding of the kernel. Have you been working on the kernel? That would be a rare combination of skills, tech & didactics. I wish I had the talent to present stuff as well as you do.
@@michaelutech4786 I've been using Linux for over 10 years, but my area of expertise is Windows, as I was a computer technician for >5 years... To be honest, in the last few months I've just decided that I need to use my general knowledge and communication skills and learn as much as possible about the kernel. It is getting better and better! I'm trying to get to 1 video a week, we'll see!
Maybe this is the wrong place to ask but I'm asking anyway. lol For those who like having Rust in the Linux kernel, how well do you think the Rust Linux kernel developers know 'C'? If they know Rust much better than C, I can understand hesitation by the C developers to incorporating more Rust into the kernel. If the Rust Linux developer is as proficient in C as they are in Rust, I think they should be able to make a more convincing argument to adopt Rust since they can advocate in 'C-like' terms/perspective vs using "because it's safer" kinds of arguments.
Rust is there because C is like Fortran to young developers. Rejecting it at this point is contributing in maliciously killing it just because you don't like it. Part of futureproofing a project is to adopt features that will be maintained by the people who use it. I don't really expect people in 100 years from now to be using C, by then it will be "too old" and younger generations prefer to do things efficiently with things that are already written rather than re-inventing the wheel for the nth time.
@@MilesPrower15 Thanks for the reply! Your point is interesting because I get the analogy of C being "ancient" to the "new crop" of developers, but given how much low-level code, like a kernel, is written in C, that changes it's scope a bit. I don't know Rust. However, I believe parts of the Rust compiler or build-chain are written in C or C++. I think JavaScript engines are written in C or C++, as are some if not all of the major browsers. I think the Windows NT kernel is also written in C and/or C++. To me, that's more 'incentive' to learn C vs something like a FORTRAN. Still, your point is well taken.
Oh, I can stop using my RX 580 after the next kernel patch? Yay! ... doesn't necessarily explain why I could replicate the problem in Windows too, but eh whatever.
@@Maple-Circuit I know right? Though to be fair the only GPUs I've ever had outright fail were nVidia ones... And I've been running ATi/AMD ever since.
Other than reading the kernel source code and hearing random people rephrase how the kernel work is there an "authoritative" source on what the kernel does and how? for example this is the first time i hear about "slab"
My biggest source outside of phoronix & LWN is the linux documentation kernel.org/doc/html/latest If you want to understand how something work, its gold. Slab is also the most complicated thing to research ever as it has 3 implementation with similar name, thank God they kill the other 2 in recent kernel...
I wonder, when Linus passes away if there will be more big changes to the kernel. I think Greg Hartman will add native support for a standardized configuration system across distributions to specify automount behavior, replacing /etc/fstab. He's fucking crazy man!
Rust in the kernel started with a weird twitter campaign foreshadowing personality clashes. I think it was Linus' first big fumble. I also disagree with the mentality about programming that Rust represents which make people think it's superior.
Changes shouldn't be pushed faster than the natural rate of your senior incumbents naturally adopting it. If you want to, let it develop independently of them. Every system of every type crashed hard, often destroying everything good that was already there with no path to become good again but within a false perception bubble, forcing change faster than natural adoption and adaptation.
@@RustIsWinning they keep saying don't need to document because it is c code...like what makes c code different from other languages XD. At the end of the day it's a bunch of "if" "then" statements.
