3 ms·

About PREEMPT_RT merge prep: are we talking about the patchset that leads to ultra-low-latency audio-friendly kernels tagged -rt, like https://aur.archlinux.org

About PREEMPT_RT merge prep: are we talking about the patchset that leads to ultra-low-latency audio-friendly kernels tagged -rt, like https://aur.archlinux.org/packages/linux-rt/ https://aur.archlinux.org/packages/linux-rt/ or https://aur.archlinux.org/packages/linux-rt-bfq/ https://aur.archlinux.org/packages/linux-rt-bfq/ ? If so, I use these for pro audio (for live dsp / effects under 5ms), and have a few questions: - Will these kernels become obsolete/unnecessary with the merge? - What about BFQ, is it going to be merged at the same time too? - This patchset has been existing for a long time. What prevented an earlier merge? - Is the merge already scheduled to happen for a specific kernel release, or "when it's ready"?

mlyle 7y ago
> Will these kernels become obsolete/unnecessary with the merge? If it merges, sure. It's nice to see it may be getting close. > What about BFQ, is it going to be merged at the same time too? BFQ merged a couple of years ago. > This patchset has been existing for a long time. What prevented an earlier merge? It's been scary in the amount of things it touches and the amount of semantics it changes. It's a big change in mindset. Many drivers have been broken or simply unsupported at times on the preempt-rt branches. More and more of the underlying infrastructure has made it in over the past couple years. > Is the merge already scheduled to happen for a specific kernel release, or "when it's ready"? Nope... the most we can say is it is "close".
- ronjouch 7y ago
  Thanks. > "BFQ merged a couple of years ago." Okay, got it. My question was driven by confusion of what exactly was package https://aur.archlinux.org/packages/linux-rt-bfq/ https://aur.archlinux.org/packages/linux-rt-bfq/ . Reading now the wiki in GitHub ( https://github.com/sirlucjan/bfq-mq-lucjan/wiki https://github.com/sirlucjan/bfq-mq-lucjan/wiki ), it's clear: > Development version of BFQ > The development version of BFQ [...] differs from the production version in that: > - it contains commits not available for that kernel version; > - it contains a lot of consistency checks to detect possible malfunctions. So, linux-rt-bfq is linux-rt, sprinkled with extra fixes to bfq unmerged yet to mainline.

mlyle 7y ago

> Will these kernels become obsolete/unnecessary with the merge? If it merges, sure. It's nice to see it may be getting close. > What about BFQ, is it going to be merged at the same time too? BFQ merged a couple of years ago. > This patchset has been existing for a long time. What prevented an earlier merge? It's been scary in the amount of things it touches and the amount of semantics it changes. It's a big change in mindset. Many drivers have been broken or simply unsupported at times on the preempt-rt branches. More and more of the underlying infrastructure has made it in over the past couple years. > Is the merge already scheduled to happen for a specific kernel release, or "when it's ready"? Nope... the most we can say is it is "close".

ronjouch 7y ago
Thanks. > "BFQ merged a couple of years ago." Okay, got it. My question was driven by confusion of what exactly was package https://aur.archlinux.org/packages/linux-rt-bfq/ https://aur.archlinux.org/packages/linux-rt-bfq/ . Reading now the wiki in GitHub ( https://github.com/sirlucjan/bfq-mq-lucjan/wiki https://github.com/sirlucjan/bfq-mq-lucjan/wiki ), it's clear: > Development version of BFQ > The development version of BFQ [...] differs from the production version in that: > - it contains commits not available for that kernel version; > - it contains a lot of consistency checks to detect possible malfunctions. So, linux-rt-bfq is linux-rt, sprinkled with extra fixes to bfq unmerged yet to mainline.