On Thu, 2006-13-07 at 10:50 -0700, Randy.Dunlap wrote:
On Mon, 19 Jun 2006 09:41:22 -0400 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.
Hi,
I have a few random
On Mon, 19 Jun 2006 09:41:22 -0400 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.
Hi,
I have a few random questions about gen-netlink.
1. Provider IDs (numbers) and names
On Tue, 2006-11-07 at 16:57 -0700, Randy.Dunlap wrote:
so make it a patch to Documentation/networking/...
I was going to when it got in better shape. Good suggestion, I will do
this soon and put it there as a patch.
I have some doc corrections, Jamal. Do I send them against
the
Jamal Hadi Salim wrote:
On Tue, 2006-11-07 at 16:57 -0700, Randy.Dunlap wrote:
so make it a patch to Documentation/networking/...
I was going to when it got in better shape. Good suggestion, I will do
this soon and put it there as a patch.
I have some doc corrections, Jamal. Do I send
On Tue, 20 Jun 2006 10:50:13 -0400 jamal wrote:
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 ! :-)
I am only allowed
On Tue, 2006-20-06 at 23:34 +0200, Thomas Graf wrote:
Ask Mr. Mashimaro has become my replacement for 8ball. Renaming
it would lead to a serious loss of coolness ;-)
;- Blame Dave for that ;-
I think if you put it in some website, I will just add a url to point to
it. Shailabh has sent me an
* jamal [EMAIL PROTECTED] 2006-06-19 09:41
// the attributes you want to own
enum {
FOOBAR_ATTR_UNSPEC,
FOOBAR_ATTR_TYPE,
FOOBAR_ATTR_TYPEID,
FOOBAR_ATTR_TYPENAME,
FOOBAR_ATTR_OPER,
/* add future attributes here */
__FOOBAR_ATTR_MAX,
On Mon, 2006-19-06 at 11:58 -0400, Shailabh Nagar wrote:
jamal wrote:
[..]
But I'm not too clear about what are the advantages of trying to limit the
number of commands registered by a given exploiter of genetlink (say TIPC or
taskstats),
other than the conventional usage of netlink.
On Mon, 2006-19-06 at 18:37 -0400, Shailabh Nagar wrote:
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
On Tue, 2006-20-06 at 10:02 +0200, Thomas Graf wrote:
* jamal [EMAIL PROTECTED] 2006-06-19 09:41
One important point about attributes in generic netlink is that
their scope is per command instead of per family as in netlink.
It's not forbidden to use the same set of attribute identifiers
for
Hello
TODO:
a) Add a more complete compiling kernel module with events.
Have Thomas put his Mashimaro example and point to it.
I guess we have a legal issue here ;)
change the name ;-
Ask Mr. Mashimaro has become my replacement for 8ball. Renaming
it would lead to a serious
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
On Mon, 19 Jun 2006, jamal wrote:
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.
Thanks for writing this up.
It seems that TIPC is multiplexing all of it's commands through
TIPC_GENL_CMD.
I wonder,
On Mon, 2006-19-06 at 11:13 -0400, James Morris wrote:
It seems that TIPC is multiplexing all of it's commands through
TIPC_GENL_CMD.
TIPC is a deviation; they had the 100 ioctls and therefore did a direct
one-to-one mapping.
I wonder, if this is how other protocols are likely to
On Mon, 19 Jun 2006, jamal wrote:
Other that TIPC the two other users i have seen use it in this manner.
But, you are right if usage tends to lean in some other way we could get
rid of it (I think TIPC is a bad example).
Ok, perhaps make a note in the docs about this and keep an eye out when
jamal wrote:
On Mon, 2006-19-06 at 11:13 -0400, James Morris wrote:
It seems that TIPC is multiplexing all of it's commands through
TIPC_GENL_CMD.
TIPC is a deviation; they had the 100 ioctls and therefore did a direct
one-to-one mapping.
I wonder, if this is how other protocols
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
17 matches
Mail list logo
