On Thu, 2005-05-19 at 11:44 -0700, David S. Miller wrote:
> From: Andrew Morton <akpm@xxxxxxxx>
> Date: Wed, 18 May 2005 23:45:52 -0700
> > > Should I ask David Miller to allocate new one specially for connector?
> > Dave?
> Giving the connector a single value 10 is OK, the rest of
> what the connector is doing in this area is not.
> I wish you hadn't put the connector into -mm, it's really
> in need of several fixups still. The bogus reuse of the
> ULOG netlink number is simply indicative of that.
And how does it indicate that it is bogus? :)
It is one netlink user that can use any socket number - and now
it is called bogus.
What other people suggest is just create some wrapper over
netlink_broadcast() and alloc_skb().
if you do think it will solve all problems, then I even will not
say anything. Point.
I just want to note, that if you want message bus, you require
at least oppsite direction, and thus input callback, and
either several socket number for each user [kobject, audit, iscsi,
xfrm - all they implement what connector already does] or
some header and thus parser in input callback, and thus
some registration mechanism. Magically it is what connector does.
And nothing more, btw.
It only allows not to rewrite the whole driver just to move
to new transport layer, only register new cn_dev device
with different method.
Ok, Dave, we all see your point, feel free to remove connector,
I will not bother people to include it yet another time...
But I believe in a month or two someone will reinvent the wheel
and create somthing similar. If it will be simple wrapper, then
it just can not solve message bus problem, only notification,
and thus someone will create it again.
P.S. smtp server from my old university years seems to still drop
your messages, sorry for that, I will kick admins again.
Crash is better than data corruption -- Arthur Grabowski
Description: This is a digitally signed message part