From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: hadi@cyberus.ca
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, netdev <netdev@oss.sgi.com>,
"David S. Miller" <davem@davemloft.net>,
James Morris <jmorris@redhat.com>,
rml@novell.com, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Netlink Connector / CBUS
Date: Tue, 05 Apr 2005 15:25:22 +0400 [thread overview]
Message-ID: <1112700322.28858.42.camel@uganda> (raw)
In-Reply-To: <1112698800.1088.50.camel@jzny.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
On Tue, 2005-04-05 at 07:00 -0400, jamal wrote:
> and, oh yeah - wheres the documentation Evgeniy? ;->
In the tree :)
Documentation/connector/connector.txt - some notes, API.
Documentation/connector/cn_test.c - kernel example.
Uses cn_netlink_send(), notification feature.
I will send today a pathc that adds in-source documentation
bits with some code cleanups.
> cheers,
> jamal
>
> On Tue, 2005-04-05 at 06:44, jamal wrote:
> > To be fair to Evgeniy I am not against the Konnector idea. I think that
> > it is a useful feature to have an easy to use messaging between
> > kernel-kernel and kernel-userspace. The fact that he leveraged netlink
> > instead of inventing things is a bonus. Having said that i have not
> > seriously scrutinized the code - and i think the idea of this new thing
> > hes tossing around called CBUS maybe pushing it.
> >
> > cheers,
> > jamal
> >
> > On Tue, 2005-04-05 at 03:34, Evgeniy Polyakov wrote:
> > > On Tue, 2005-04-05 at 01:10 -0400, Herbert Xu wrote:
> > > >On Tue, Apr 05, 2005 at 11:03:16AM +0400, Evgeniy Polyakov wrote:
> > > >>
> > > >> I received comments and feature requests from Herbert Xu and Jamal Hadi
> > > >> Salim,
> > > >> almost all were successfully resolved.
> > > >
> > > >Please do not construe my involvement in these threads as endorsement
> > > >for this system.
> > >
> > > Sure.
> > > I remember you are against it :).
> > >
> > > >In fact to this day I still don't understand what problems this thing is
> > > >meant to solve.
> > >
> > > Hmm, what else can I add to my words?
> > > May be checking the size of the code needed to broadcast kobject changes
> > > in kobject_uevent.c for example...
> > > Netlink socket allocation + skb handling against call to cn_netlink_send().
> > >
> > > >--
> > > >Visit Openswan at http://www.openswan.org/
> > > >Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
> > > >Home Page: http://gondor.apana.org.au/~herbert/
> > > >PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
> > >
> >
> >
> >
--
Evgeniy Polyakov
Crash is better than data corruption -- Arthur Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-05 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 5:05 Netlink Connector / CBUS James Morris
2005-04-05 5:10 ` James Morris
2005-04-05 7:08 ` Evgeniy Polyakov
2005-04-05 7:34 ` Evgeniy Polyakov
2005-04-05 8:11 ` Guillaume Thouvenin
2005-04-05 10:44 ` jamal
2005-04-05 11:00 ` jamal
2005-04-05 11:25 ` Evgeniy Polyakov [this message]
2005-04-05 7:03 ` Evgeniy Polyakov
2005-04-05 7:10 ` Herbert Xu
2005-04-05 16:54 ` James Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1112700322.28858.42.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rml@novell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.