From: jamal <hadi@cyberus.ca>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [GENL]: Provide more information to userspace about registered genl families
Date: Thu, 31 Aug 2006 17:46:52 -0400 [thread overview]
Message-ID: <1157060812.5297.51.camel@jzny2> (raw)
In-Reply-To: <20060831212129.GF3470@postel.suug.ch>
Useful stuff. There are things along these lines that i have been
contemplating myself.
I think it would be valuable to specify a set of flags for filtering
what gets sent to user space instead of unconditionally.
Example,
filter level 0:
- what we have before your patch
filter level 1:
- protocol version
- header size
- maximum number of attributes
filter level 2:
- the rest of the stuff you have
What netlink does today to filter at user space is something that can be
avoided with the above (an improvement in my opinion if you have a lot
of genl items in the kernel).
cheers,
jamal
On Thu, 2006-31-08 at 23:21 +0200, Thomas Graf wrote:
> Additionaly exports the following information when providing
> the list of registered generic netlink families:
> - protocol version
> - header size
> - maximum number of attributes
>
> - list of available operations including
> - id
> - flags
> - avaiability of policy and doit/dumpit function
>
> libnl HEAD provides a utility to read this new information:
>
> 0x0010 nlctrl version 1
> hdrsize 0 maxattr 6
> op GETFAMILY (0x03) [POLICY,DOIT,DUMPIT]
> 0x0011 NLBL_MGMT version 1
> hdrsize 0 maxattr 0
> op unknown (0x02) [DOIT]
> op unknown (0x03) [DOIT]
> ....
>
next prev parent reply other threads:[~2006-08-31 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 21:21 [GENL]: Provide more information to userspace about registered genl families Thomas Graf
2006-08-31 21:46 ` jamal [this message]
2006-09-01 6:48 ` Johannes Berg
2006-09-01 12:22 ` jamal
2006-09-01 12:25 ` Johannes Berg
2006-09-01 13:00 ` jamal
2006-09-03 12:04 ` Johannes Berg
2006-09-18 7:02 ` David Miller
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=1157060812.5297.51.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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