Re: [GIT PULL] kdbus for 4.1-rc1

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Tue, Apr 21, 2015 at 03:18:35PM +0200, Olivier Galibert wrote:
> On Tue, Apr 21, 2015 at 12:31 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > Bringing up SCM_RIGHTS means that this is not going to be a bus system
> > at all.  One principal design goal is to _not_ have peer-to-peer
> > connections between all communicating parties, but rather one connection
> > to a central component.  If that component is not in the kernel, it has
> > to be a userspace deamon, which in turn has all of the issues that
> > dbus-daemon currently has.
> 
> You're not making sense there.  If there is no daemon, then you're
> peer-to-peer, because there's no central component.

The kernel is the central component, as implemented in the patches.

> If you consider the kernel the central component, then peer-to-peer is
> almost impossible by definition.

Um, no, they go through the kernel for that model as well, same
interface, it just depends on the type of message that you are sending
as to who the recipients are (single or more than one.)

> It seems that almost everybody here thinks that the plumbing (e.g.
> transmitting messages in-order with multicasting) should be separated
> from the policy (who communicates with who), possibly leveraging the
> packet filtering infrastructure to implement the decided policy.  What
> it is you reject about that point of view, which seems relatively
> normal when you think about building a collection of useful tools?

The plumbing is "separated" from the policy in that they are different
data structures, but you have to have the policy in order to know who to
connect with whom, otherwise it just doesn't work.

How would packet filtering work here for this type of decision making?
That's a much more complex interface than what we have implemented,
don't you agree?

thanks,

greg k-h