lkml.org 
[lkml]   [2014]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kdbus: add code for buses, domains and endpoints
On 21.11.2014 06:02, Greg Kroah-Hartman wrote:
> From: Daniel Mack <daniel@zonque.org>
>
> Add the logic to handle the following entities:
>
> Domain:
> A domain is an unamed object containing a number of buses. A
> domain is automatically created when an instance of kdbusfs
> is mounted, and destroyed when it is unmounted.
> Every domain offers its own "control" device node to create
> buses. Domains have no connection to each other and cannot
> see nor talk to each other.
>
> Bus:
> A bus is a named object inside a domain. Clients exchange messages
> over a bus. Multiple buses themselves have no connection to each
> other; messages can only be exchanged on the same bus. The default
> entry point to a bus, where clients establish the connection to, is
> the "bus" device node /dev/kdbus/<bus name>/bus. Common operating
> system setups create one "system bus" per system, and one "user
> bus" for every logged-in user. Applications or services may create
> their own private named buses.

might need a resync with the documentation.

Bus:
A bus is a named object inside a domain. Clients exchange messages
over a bus. Multiple buses themselves have no connection to each other;
messages can only be exchanged on the same bus. The default entry point to
a bus, where clients establish the connection to, is the "bus" file
/sys/fs/kdbus/<bus name>/bus.
Common operating system setups create one "system bus" per system, and one
"user bus" for every logged-in user. Applications or services may create
their own private named buses. See section 5 for more details.




\
 
 \ /
  Last update: 2014-11-21 09:41    [W:0.295 / U:0.012 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site