49:19 π€£π€£ Oh boy, the way you say βschedulerβ π I thought itβs a US vs British pronunciation thing but this is something completely wild π
Maybe, but Linus destroyed his reputation worldwide bringing politics, better if he resigns. The Linux project as global collaboration is very shaky idea now, if same people still there. I thought collaboration projects are self-regulated, but we have here something authoritarian. Pandora box opened, next are Middle East and Asia regions people, the separation started.
RT is all about deterministic behavior not hard time scales. The point is knowing exactly how a complex system will behave. For example, knowing how much cpu time a processes will have and when. It does not mean your "script" will always run in exactly the same time, just in a predictable time. In the CNC example, inputs (interrupts) will be processed in a known time range.
Excuse me, pardon that i only understood 20% of these hype Just a quick dumb and useless question. on gaming, will 6.12 have better vrr (freesync) and better vram management?
Rust. I would not be bothered were it not for the annoying Rust fanboys over-hyping "memory safety" and the like. I tried using Rust some years back for an ML project and spent 90% of my time fighting the borrow checker. I've could've been done had I used C++ — and I know how to write memory-safe code in C++.
So now I am implementing that ML project in Haskell. And I have a bad taste in my mouth for Rust. I really don't like it when my tools second-guess what I want to do, as I tend to know what I am doing after decades of software engineering. Duh.
A part of the problem with removing the Russian maintainers was that because of legal reasons the developers who removed them couldn't really talk about them. That's where things really got messed up.
1:04:15 I would guess this change was noticed by mutation testing which intentionally breaks code logic (here probably adding `&& false` to the whole if test to disable the whole branch) and instead of kernel crash, they saw a huge performance boost. After that it was time to figure out why it was okay to ignore that whole branch.
Can you imagine the combination of the new EDAC feature with real time Linux ? If we can guarantee how long a single fault takes and the rest of the system continues in the right time, would be amazing. Maybe we now can.
I think the Rust progress should be followed by monitoring the amount of crashes per 100k lines. If the Rust code actually gets less (critical? memory corruption?) bugs than C code, then the transition to more Rust makes sense even if it's painful. If I've understood correctly, there's still too little Rust code to have statistical trust in the results right now so kernel community must keep adding Rust until the results are statistically meaningful.
If Rust code is statistically less broken then it means that Rust usage should increase in the kernel. If Rust code is equally broken to C then I'm not sure if adding any new Rust code is worth the effort. This far the Apple AGX GPU driver has been the most complex Rust part and that has shown a lot of promise already.
Pretty certain maintaining any older technology, like Firewire, is for existing deployments of production machines. (or things like cars or uses in buildings or airplanes, etc.) Anything which has a long life as a device.
49:20 I thought EEVDF already replaced CFS in Linux 6.6?
It was noted to be "incomplete" at the time iirc.
49:19 π€£π€£ Oh boy, the way you say βschedulerβ π
I thought itβs a US vs British pronunciation thing but this is something completely wild π
has there ever been someone so infamous as Kent in the LKML? idk if Stallman was ever on it, but more interesting examples preferably XD
i still dont get how windows can be more popular than linux
Thereβs no way there canβt be an 8 minute version of this. Over an hour for a kernel changelog is nuts
Skedjewler?
I did sudo pacman -Syu and nothing started on fire.
3888.9% faster because of #Rust….
Maybe, but Linus destroyed his reputation worldwide bringing politics, better if he resigns. The Linux project as global collaboration is very shaky idea now, if same people still there. I thought collaboration projects are self-regulated, but we have here something authoritarian. Pandora box opened, next are Middle East and Asia regions people, the separation started.
RT is all about deterministic behavior not hard time scales. The point is knowing exactly how a complex system will behave. For example, knowing how much cpu time a processes will have and when. It does not mean your "script" will always run in exactly the same time, just in a predictable time. In the CNC example, inputs (interrupts) will be processed in a known time range.
Glad I found this channel.
stop saying scheduler like that
A shot for every time you say sche JULER π haahahah, love the video, no disrespect π
amazing video!
Excuse me, pardon that i only understood 20% of these hype
Just a quick dumb and useless question.
on gaming, will 6.12 have better vrr (freesync) and better vram management?
Youtube algorithm, just recommended this video, and channel that explains in depth an Linux Kernel release π
i use fw mofo
The way you pronounce "management"π
Rust. I would not be bothered were it not for the annoying Rust fanboys over-hyping "memory safety" and the like. I tried using Rust some years back for an ML project and spent 90% of my time fighting the borrow checker. I've could've been done had I used C++ — and I know how to write memory-safe code in C++.
So now I am implementing that ML project in Haskell. And I have a bad taste in my mouth for Rust. I really don't like it when my tools second-guess what I want to do, as I tend to know what I am doing after decades of software engineering. Duh.
Fuck ruZZia
Take a shot for every skeyuler.
Not sure what benefits did russian maintainers have by contributing to the freely distributed kernel. Now they have more time to spend working on KGB.
nice…
A part of the problem with removing the Russian maintainers was that because of legal reasons the developers who removed them couldn't really talk about them. That's where things really got messed up.
1:04:15 I would guess this change was noticed by mutation testing which intentionally breaks code logic (here probably adding `&& false` to the whole if test to disable the whole branch) and instead of kernel crash, they saw a huge performance boost. After that it was time to figure out why it was okay to ignore that whole branch.
Can you imagine the combination of the new EDAC feature with real time Linux ? If we can guarantee how long a single fault takes and the rest of the system continues in the right time, would be amazing. Maybe we now can.
I think the Rust progress should be followed by monitoring the amount of crashes per 100k lines. If the Rust code actually gets less (critical? memory corruption?) bugs than C code, then the transition to more Rust makes sense even if it's painful. If I've understood correctly, there's still too little Rust code to have statistical trust in the results right now so kernel community must keep adding Rust until the results are statistically meaningful.
If Rust code is statistically less broken then it means that Rust usage should increase in the kernel. If Rust code is equally broken to C then I'm not sure if adding any new Rust code is worth the effort. This far the Apple AGX GPU driver has been the most complex Rust part and that has shown a lot of promise already.
Pretty certain maintaining any older technology, like Firewire, is for existing deployments of production machines. (or things like cars or uses in buildings or airplanes, etc.) Anything which has a long life as a device.