V4 Of KDBUS Posted For The Linux Kernel

[phoronix]

Phoronix: V4 Of KDBUS Posted For The Linux Kernel

KDBUS didn't make it for Linux 4.0 but version four of the KDBUS patches were posted today for review, which gives out hope we could see this in-kernel IPC interface based on D-Bus merged for Linux 4.1...

http://www.phoronix.com/scan.php?page=news_item&px=KDBUS-V4-Linux-Kernel

[mark45]

When you go thru the code review process you get the impression the code will always contain areas which need to be fixed. This process is so pedantic that mostly one perseveres only because one is paid.

[gens]

"...can potentially be used for [snip] Wayland IPC needs"
oh god no, that would be horrible


also Crapaudio should have had a proper mmaped ipc from the start, like all other "sound servers" do

[przemoli]

When you go thru the code review process you get the impression the code will always contain areas which need to be fixed. This process is so pedantic that mostly one perseveres only because one is paid.

And that is why despite millions of lines of code, tens of thousands of contributors, and thousands of companies paying for that code...

Quality is good.

Linux kernel have policy of stable public API. KDBUS will have public API hence extra pedantic reviews.

[justmy2cents]

"...can potentially be used for [snip] Wayland IPC needs"
oh god no, that would be horrible


also Crapaudio should have had a proper mmaped ipc from the start, like all other "sound servers" do

yea, because coders have nothing to do. reinventing incompatible IPCs is such a nice way to spend time

[blackout23]

Ship it!

[balouba]

When you go thru the code review process you get the impression the code will always contain areas which need to be fixed. This process is so pedantic that mostly one perseveres only because one is paid.

Not sure why that would be negative. The kernel is probably the most critical piece of the OS.

Next thing you'll do is complain about linux being unclean and unstable and how we've arrived there. Well, that's because of people like you. Complaining about things being too pedantic, not pedantic enough, etc.

Also, never your fault, and god forbid that you go submit your own patches instead.

[Guest]

Ship it!

Maybe bit premature, I've been testing kdbus from latest git tree for about a year now and it's FAR from stable. Over last 6 months there were 2 ABI breakages that made system unbootable for days (till both kdbus and systemd repository got synced).

Distribution maintainers aren't complete morrons and end users wouldn't be likely affected but if systemd has problem to maintain compatibility with kdbus, how can we expect third party projects to support kdbus (you could make argument that systemd provides compat layer for this and their own interfaces, but as I said, two breakages that made system unbootable).

[interested]

Maybe bit premature, I've been testing kdbus from latest git tree for about a year now and it's FAR from stable. Over last 6 months there were 2 ABI breakages that made system unbootable for days (till both kdbus and systemd repository got synced).

Several of the ABI breaks was caused by changes caused by the code review (and fully documented in the Git log AFAIK). No kernel feature is per definition stable until it is mainlined.
So far kdbus have had an excellent peer review on LKML by Andy Lutomirski and M. Kerrisk that went through both security and documentation issues.

Interesting to watch if anybody still can turn up any issues, but I wouldn't be surprised if there are only minor issues left with kdbus v4.

[liam]

"...can potentially be used for [snip] Wayland IPC needs"
oh god no, that would be horrible


also Crapaudio should have had a proper mmaped ipc from the start, like all other "sound servers" do

... you can absolutely access alsa through mmap. It's an option you can conf