1. 26 4月, 2007 4 次提交
  2. 11 2月, 2007 1 次提交
  3. 07 12月, 2006 2 次提交
  4. 03 12月, 2006 5 次提交
  5. 23 9月, 2006 4 次提交
  6. 01 7月, 2006 1 次提交
  7. 30 6月, 2006 1 次提交
  8. 27 3月, 2006 1 次提交
  9. 14 2月, 2006 1 次提交
  10. 14 1月, 2006 1 次提交
  11. 04 1月, 2006 1 次提交
  12. 10 11月, 2005 1 次提交
    • T
      [NETLINK]: Generic netlink family · 482a8524
      Thomas Graf 提交于
      The generic netlink family builds on top of netlink and provides
      simplifies access for the less demanding netlink users. It solves
      the problem of protocol numbers running out by introducing a so
      called controller taking care of id management and name resolving.
      
      Generic netlink modules register themself after filling out their
      id card (struct genl_family), after successful registration the
      modules are able to register callbacks to command numbers by
      filling out a struct genl_ops and calling genl_register_op(). The
      registered callbacks are invoked with attributes parsed making
      life of simple modules a lot easier.
      
      Although generic netlink modules can request static identifiers,
      it is recommended to use GENL_ID_GENERATE and to let the controller
      assign a unique identifier to the module. Userspace applications
      will then ask the controller and lookup the idenfier by the module
      name.
      
      Due to the current multicast implementation of netlink, the number
      of generic netlink modules is restricted to 1024 to avoid wasting
      memory for the per socket multiacst subscription bitmask.
      Signed-off-by: NThomas Graf <tgraf@suug.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      482a8524