[lkml]   [2015]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [GIT PULL] kdbus for 4.1-rc1
On 04/16/2015 12:08 AM, One Thousand Gnomes wrote:
>> When trying to split apart problems, for dbus it's important to keep
>> ordering guarantees.
> Yes I assumed that - minus disconnection/reconnect and running out of
> queue space. Some users also want priority queueing (with or without the
> guarantee for the same priority). Many of the other systems that can use
> a fast multicast messaging system have priority queues - which is one
> reason the existing POSIX messaging has priority.

And so does kdbus. By default, strict ordering is enforced when messages
are received, but optionally, that action may be constrained to messages
of a minimal priority. This allows for use cases where timing critical
data is interleaved with control data on the same connection. That's
described in kdbus.message(7), and is also covered by test cases.


 \ /
  Last update: 2015-04-16 15:41    [W:0.540 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site