Originally posted by Dubhthach
View Post
Announcement
Collapse
No announcement yet.
Bringing D-Bus Into The Linux Kernel
Collapse
X
-
Originally posted by RealNC View PostLet's move Firefox into the kernel too. I can post benchmarks then showing how faster it is
Or to make a better analogy: Paying a bus driver to leave his bus and stand around outside the exact moment nobody needs to driven and have him haste back into the bus whenever customers are around makes no sense. Yet with D-Bus you advocate that.
And once again: The kernel is modular - you don't want D-Bus don't build it.
Comment
-
Originally posted by bilbao View PostWith plasma fire you mean. And all the devs who had this idea. Then spread the dust through space and lets never talk about it again!
I'm thinking that we just take off and nuke it from orbit- it's the only way to be sure. >:-D
Comment
-
Originally posted by DeepDayze View PostDCOP is a KDE thing not a general userspace message bus and definitely old and has reached its limits, thus dbus was born. Also Gnome just started using dbus as well so it isn't just a KDE thing now any longer and it has gotten the same benefits as KDE did.
Comment
-
Originally posted by fabiank22 View PostThe only reason for the massive speedup in D-Bus is because D-Bus is a userspace daemon that has to do A LOT of switching to Kernel Mode whenever it's used. Firefox needs to do nothing in kernel mode.
Any other arguments why moving D-Bus into kernelspace is supposedly a good idea, while moving firefox isn't?
Comment
-
Originally posted by rohcQaH View PostThere are more messages between Firefox and X than D-Bus messages on my whole desktop. If it's just about eliminating the system calls and memory copies, moving either Firefox or X into the kernel would save way more CPU cycles than moving D-Bus.
Any other arguments why moving D-Bus into kernelspace is supposedly a good idea, while moving firefox isn't?
Comment
Comment