From: Neil Horman <nhorman@tuxdriver.com>
To: netdev@vger.kernel.org
Cc: Neil Horman <nhorman@tuxdriver.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
James Chapman <jchapman@katalix.com>,
David Miller <davem@davemloft.net>
Subject: [PATCH 0/3] net: implement auto-loading of generic netlink modules
Date: Tue, 29 May 2012 15:30:39 -0400 [thread overview]
Message-ID: <1338319842-18395-1-git-send-email-nhorman@tuxdriver.com> (raw)
Eric D. recently noted that the drop_monitor module didn't autoload when the
dropwatch user space utility started. Looking into this I noted that theres no
formal macro set to define module aliases that can be used by a request module
call in the generic netlink family lookup path. Currenlty the
net-pf-*-proto-*-type-<n> format is used, but the macros which form this expect
<n> to be a well defined integer, which generic netlink doesn't use for family
definitions. So this series creates a new macro that create a
net-pf-*-proto-*-name format where name can be any arbitrary string, allowing us
to apend family-<x> where x is a generic netlink family name. With these
macros, we can easily autoload modules that register generic netlink families
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
CC: Eric Dumazet <eric.dumazet@gmail.com>
CC: James Chapman <jchapman@katalix.com>
CC: David Miller <davem@davemloft.net>
next reply other threads:[~2012-05-29 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 19:30 Neil Horman [this message]
2012-05-29 19:30 ` [PATCH 1/3] net: add MODULE_ALIAS_NET_PF_PROTO_NAME Neil Horman
2012-05-29 19:30 ` [PATCH 2/3] genetlink: Build a generic netlink family module alias Neil Horman
2012-05-29 19:30 ` [PATCH 3/3] drop_monitor: Add module alias to enable automatic module loading Neil Horman
2012-05-30 2:34 ` [PATCH 0/3] net: implement auto-loading of generic netlink modules 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=1338319842-18395-1-git-send-email-nhorman@tuxdriver.com \
--to=nhorman@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
/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).