[lkml]   [2005]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [1/1] connector/CBUS: new messaging subsystem. Revision number next.
On Tue, 26 Apr 2005 12:31:58 -0500
Dmitry Torokhov <> wrote:

> > There may not be the same work with different data.
> >
> Ugh, that really blows. Now every user of a particular message type
> has to coordinate efforts with other users of the same message type...
> Imability to "fire and forget" undermines usefulness of whole
> connector. How will you for example implement hotplug notification
> over connector? Have kobject_hotplug wait and block other instances?
> But wait on what?

This is a simple load balancing schema.
Netlink messages may be dropped in socket queue when
they are bing delivered to userspace - this is the same -
if work queue can not be scheduled, message will be dropped,
but in this case userspace also can not be scheduled
and message will be dropped.

> --
> Dmitry

Evgeniy Polyakov

Only failure makes us experts. -- Theo de Raadt
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-04-26 20:09    [W:0.042 / U:73.964 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site