From: Shailabh Nagar <nagar@watson.ibm.com>
To: hadi@cyberus.ca
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Thomas Graf <tgraf@suug.ch>, Jay Lan <jlan@engr.sgi.com>,
Per Liden <per.liden@ericsson.com>
Subject: Re: [DOC]: generic netlink
Date: Mon, 19 Jun 2006 18:37:55 -0400 [thread overview]
Message-ID: <44972743.3040904@watson.ibm.com> (raw)
In-Reply-To: <1150724482.5815.48.camel@jzny2>
jamal wrote:
> Folks,
>
> Attached is a document that should help people wishing to use generic
> netlink interface. It is a WIP so a lot more to go if i see interest.
> The doc has been around for a while, i spent part of yesterday and this
> morning cleaning it up. If you have sent me comments before, please
> forgive me for having misplaced them - just send again.
Jamal,
Completing the documentation on generic netlink usage will definitely be
useful. I'd be happy to help out with this since I've recently gone through
trying to understand and use genetlink for the taskstats interface. Hopefully
this will help other users like me who aren't netlink experts to begin with !
I've sent you a patch to the document that attempts to cover the following
TODOS (didn't see any point sending it to the whole list since its harder to
read patches to documentation). Pls use as you see fit.
> TODO:
> a) Add a more complete compiling kernel module with events.
> Have Thomas put his Mashimaro example and point to it.
(not the Mashimaro example, nor a completly compiled module but snippets
of pseudo code taken from the user space program used in taskstats development,
modified to the foobar example you've used)
> b) Describe some details on how user space -> kernel works
> probably using libnl??
> c) Describe discovery using the controller..
I'll provide another patch that will cover d) and e) in the set below, again
in the context of the foobar example, which might need to be modified a bit.
> d) talk about policies etc
> e) talk about how something coming from user space eventually
> gets to you.
> f) Talk about the TLV manipulation stuff from Thomas.
> g) submit controller patch to iproute2
One point...does d), f) etc. belong in a separate doc describing usage
of netlink attributes ? Its useful here too but not directly related to
genetlink perhaps.
> PS:- I dont have a good place to put this doc and point to, hence the
> 17K attachment
>
http://www.kernel.org/pub/linux/kernel/people/hadi/ ?
(unless your permissions have been revoked for lack of use ! :-)
Having the current document will be useful to see what edits have been accepted
and work on that instead of the original.
--Shailabh
next prev parent reply other threads:[~2006-06-19 22:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 13:41 [DOC]: generic netlink jamal
2006-06-19 15:13 ` James Morris
2006-06-19 15:28 ` jamal
2006-06-19 15:54 ` James Morris
2006-06-20 12:59 ` jamal
2006-06-19 15:58 ` Shailabh Nagar
2006-06-20 13:19 ` jamal
2006-06-19 22:37 ` Shailabh Nagar [this message]
2006-06-20 14:50 ` jamal
2006-07-11 23:57 ` Randy.Dunlap
2006-07-12 11:30 ` Jamal Hadi Salim
2006-07-12 15:16 ` Shailabh Nagar
2006-06-20 8:02 ` Thomas Graf
2006-06-20 15:01 ` jamal
2006-06-20 21:34 ` Thomas Graf
2006-06-22 19:07 ` jamal
2006-07-13 17:50 ` Randy.Dunlap
2006-07-14 11:43 ` Jamal Hadi Salim
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=44972743.3040904@watson.ibm.com \
--to=nagar@watson.ibm.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=jlan@engr.sgi.com \
--cc=netdev@vger.kernel.org \
--cc=per.liden@ericsson.com \
--cc=tgraf@suug.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).