On Tue, 2010-11-30 at 10:51 -0700, Jason Gunthorpe wrote: > On Tue, Nov 30, 2010 at 02:56:41PM +0200, Nir Muchtar wrote: > > > Do you mean adding this to ib_core? I'm not sure we want to > > autoload ib_core whenever the userspace asks for "socket(PF_NETLINK, > > SOCK_RAW, NETLINK_INFINIBAND)" What's wrong with receiving a > > "protocol not supported" error? If ib_core is not loaded then > > there's no data anyway. Am I missing other possible effects of > > MODULE_ALIAS here? > > It seems to be kernel policy to annotate this sort of autoload > meta-data. > > If the module is demand loaded or not is a userspace choice. > > Apps using this should handle both cases. > > Jason
MODULE_ALIAS_PF_PROTO is used by the netlink layer once netlink_create is called by userspace (with request_module), So it is used by dedicated netlink modules such as inet_diag and nf_netlink. netlink_scsitransport is a closer example to our design, where there is no use of MODULE_ALIAS. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
