netdev
[Top] [All Lists]

Re: [1/1] connector/CBUS: new messaging subsystem. Revision number next.

To: dtor_core@xxxxxxxxxxxxx
Subject: Re: [1/1] connector/CBUS: new messaging subsystem. Revision number next.
From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
Date: Tue, 26 Apr 2005 22:03:54 +0400
Cc: dmitry.torokhov@xxxxxxxxx, netdev@xxxxxxxxxxx, Greg KH <greg@xxxxxxxxx>, Jamal Hadi Salim <hadi@xxxxxxxxxx>, Kay Sievers <kay.sievers@xxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, James Morris <jmorris@xxxxxxxxxx>, Guillaume Thouvenin <guillaume.thouvenin@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Andrew Morton <akpm@xxxxxxxx>, Thomas Graf <tgraf@xxxxxxx>, Jay Lan <jlan@xxxxxxxxxxxx>
In-reply-to: <d120d50005042610317961a564@mail.gmail.com>
Organization: MIPT
References: <20050411125932.GA19538@uganda.factory.vocord.ru> <d120d5000504260857cb5f99e@mail.gmail.com> <20050426202437.234e7d45@zanzibar.2ka.mipt.ru> <d120d50005042610317961a564@mail.gmail.com>
Reply-to: johnpol@xxxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Tue, 26 Apr 2005 12:31:58 -0500
Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> 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

<Prev in Thread] Current Thread [Next in Thread>