Originally posted by pingufunkybeat
View Post
Announcement
Collapse
No announcement yet.
Bringing D-Bus Into The Linux Kernel
Collapse
X
-
Why would this benefit performance exactly? What sort of overhead is intrinsically connected to user-space code (i.e. most of the code you run) aside from the few cycles required to switch x86 into protected mode? If there's that much to be gained by moving stuff into the kernel then I'd call that a design flaw elsewhere having nothing to do with dbus.
Comment
-
Step 1: design Yet Another Ugly and Overengineered IPC System (YAUOIS)
Step 2: move it to the kernel to overcome the problems caused by bad design decisions.
Seriously, I doubt this will be accepted. Android is already trying to push in their own (YAUOIS)...how many of the do we need? Can't D-Bus use the Android crap?
Comment
-
Originally posted by diegocg View PostStep 1: design Yet Another Ugly and Overengineered IPC System (YAUOIS)
Step 2: move it to the kernel to overcome the problems caused by bad design decisions.
Secondly those are not "bad design decisions", D-Bus was created with KDE/The Desktop in mind, not with embedded systems. My normal CPU can handle the (small) overhead, but ARM/Snapdragon-Phones and devices?
Also Power Consumption is a good point, Kernel Space = less wakeup calls due to context switching. This is Computer Science 101.
Comment
-
Let's move Firefox into the kernel too. I can post benchmarks then showing how faster it is. While we're at it, move everything into the kernel. A distro then consists of a 20GB vmlinuz kernel image. It will be very fast, I guarantee it, since everything is in the kernel.
Of course, in order to do updates, you have to update the whole kernel. But who gives a fsck? They did it with drivers. Let's do it with everything else too.
Comment
-
-
Originally posted by fabiank22 View PostOh yeah, what exactly is "ugly" and "Overengineered"? Do you have any idea how D-Bus works or have developed with it at all? D-Bus was created to adress real problems(e.g. DCOP being old and not up to the task anymore), and also has been around for a while now. There's a freedesktop spec and all.
Secondly those are not "bad design decisions", D-Bus was created with KDE/The Desktop in mind, not with embedded systems. My normal CPU can handle the (small) overhead, but ARM/Snapdragon-Phones and devices?
Also Power Consumption is a good point, Kernel Space = less wakeup calls due to context switching. This is Computer Science 101.
Comment
Comment