Linux 6.7 Continues Work On printk Threaded Printing

[phoronix]

Phoronix: Linux 6.7 Continues Work On printk Threaded Printing

One of the last major blockers before the remaining real-time "PREEMPT_RT" patches can be upstreamed is sorting out threaded / atomic console printing. With the in-development Linux 6.7 kernel, there's been more work upstreamed in that endeavor...

https://www.phoronix.com/news/Linux-6.7-printk

[timofonic]

Bcachefs, then PREEMPT_RT and have RT Linux in mainline! It would be a dream come true!

[onlyLinuxLuvUBack]

They just need to rewrite it in rust

[caligula]

Bcachefs, then PREEMPT_RT and have RT Linux in mainline! It would be a dream come true!

They still need to sort out the Wayland fiasco. Having rt kernel and Pipewire 1.0 might be sufficient for a DAW setup, but people also need tear-free wide gamut HDR 8k displays with VRR, daisy chaining, 3d stereo, and color management on Wayland. On top of that, everything should be rendered with vulkan and zink. And the render code needs to use Rust. Also the memory folio stuff should be finalized. All wifi drivers stabilize from the staged status. Btrfs raid5 should work 100%. Fwupd should have support for all hardware. And instead of uefi we should use open source bios.

This is basically the bare minimum before we can say it's the year of Linux desktop.

[Ironmask]

They still need to sort out the Wayland fiasco. Having rt kernel and Pipewire 1.0 might be sufficient for a DAW setup, but people also need tear-free wide gamut HDR 8k displays with VRR, daisy chaining, 3d stereo, and color management on Wayland. On top of that, everything should be rendered with vulkan and zink. And the render code needs to use Rust. Also the memory folio stuff should be finalized. All wifi drivers stabilize from the staged status. Btrfs raid5 should work 100%. Fwupd should have support for all hardware. And instead of uefi we should use open source bios.

This is basically the bare minimum before we can say it's the year of Linux desktop.

I'm not sure if this is satire or not, but you do know the majority of RT kernels are going to be in headless microcontrollers, right?
I don't understand why so many posters here don't know what a realtime OS is for. You're pretty much never going to be interacting with one directly.

[caligula]

I'm not sure if this is satire or not, but you do know the majority of RT kernels are going to be in headless microcontrollers, right?
I don't understand why so many posters here don't know what a realtime OS is for. You're pretty much never going to be interacting with one directly.

Many of the posters are ordinary home PC users who want the best hardware they can afford, and also all the possible features that can be implemented in software. Real-time audio with nanosecond latencies is important for high fidelity audio playback. Many consumers also buy high end medium format cameras and really need the widest possible gamut and pixel count that can be manufactured with current panel technologies. E.g. 4k is only about 8 megapixels. Even 8k is only about 36 megapixels. Many DSLRs have 50 MPix sensors. Mobile phones already 192 MPix.

Good example is the latest M3 laptop from Apple. 128 GB of RAM, 8 TB of SSD, 16 cores.

[Volta]

Many of the posters are ordinary home PC users who want the best hardware they can afford, and also all the possible features that can be implemented in software. Real-time audio with nanosecond latencies is important for high fidelity audio playback. Many consumers also buy high end medium format cameras and really need the widest possible gamut and pixel count that can be manufactured with current panel technologies. E.g. 4k is only about 8 megapixels. Even 8k is only about 36 megapixels. Many DSLRs have 50 MPix sensors. Mobile phones already 192 MPix.

Good example is the latest M3 laptop from Apple. 128 GB of RAM, 8 TB of SSD, 16 cores.

You got an answer, but you failed to understand a thing. RT is not for you and it's not for apple noobs.

[Ironmask]

Many of the posters are ordinary home PC users who want the best hardware they can afford, and also all the possible features that can be implemented in software. Real-time audio with nanosecond latencies is important for high fidelity audio playback. Many consumers also buy high end medium format cameras and really need the widest possible gamut and pixel count that can be manufactured with current panel technologies. E.g. 4k is only about 8 megapixels. Even 8k is only about 36 megapixels. Many DSLRs have 50 MPix sensors. Mobile phones already 192 MPix.

Good example is the latest M3 laptop from Apple. 128 GB of RAM, 8 TB of SSD, 16 cores.

Is this AI generated?

[caligula]

You got an answer, but you failed to understand a thing. RT is not for you and it's not for apple noobs.

How do you know that? There are literally billions of consumers consuming audio streams. They spend tens of thousands of dollars on high end streamers, amplifiers, DACs, etc. The speakers easily cost hundreds of thousands of USD. Even headphones easily cost 10k. These people need the highest quality. Hard-realtime music playback with no pops, cracks, distortions, delays, xruns. Xruns are absolutely not tolerated when listening to music streams. RT kernel would allow them to use computers instead of expensive dedicated hardware. Many world class record studios spend less on hardware than these consumers.

[Ironmask]

How do you know that? There are literally billions of consumers consuming audio streams. They spend tens of thousands of dollars on high end streamers, amplifiers, DACs, etc. The speakers easily cost hundreds of thousands of USD. Even headphones easily cost 10k. These people need the highest quality. Hard-realtime music playback with no pops, cracks, distortions, delays, xruns. Xruns are absolutely not tolerated when listening to music streams. RT kernel would allow them to use computers instead of expensive dedicated hardware. Many world class record studios spend less on hardware than these consumers.

The thing you're describing would still be a headless dedicated unit.
I don't think you've ever tried to use an RTOS on a desktop. The UI is literally unresponsive. Your computer would be entirely busy doing decoding or whatever you're trying to make it do, and you'd be unable to do anything else. GUIs and RTOSes do not mix.
More over, you don't need an RTOS to do decoding, you can just as easily use drivers to communicate to the kernel that it's a high priority task anyway. RTOS is pretty much exclusively for robotics, it's adjacent to an exokernal, you're basically writing bare-metal software and are entirely responsible for all operations in the OS, because anything could cause your software to miss a deadline. Especially GUIs, which is why they do not run on RTOSes, not without either making the GUI unresponsive or making everything else miss deadlines (ruining the point of an RTOS).

And I swear to god you sound like a marketing agent, I really can't tell if this is AI generated or just got off work and are still in work mode.