| /openbmc/linux/Documentation/userspace-api/netlink/ |
| H A D | intro.rst | 4 Introduction to Netlink
7 Netlink is often described as an ioctl() replacement.
12 To achieve this Netlink uses a minimal fixed-format metadata header
24 Netlink communication happens over sockets, a socket needs to be
36 A very simplified flow of a Netlink "call" will therefore look
48 Netlink also provides natural support for "dumping", i.e. communicating
70 it is opening a Netlink socket, with all headers provided by the user
71 (hence NETLINK, RAW). The last argument is the protocol within Netlink.
75 Classic vs Generic Netlink
78 Initial implementation of Netlink depended on a static allocation
[all …]
|
| H A D | netlink-raw.rst | 4 Netlink specification support for raw Netlink families
7 This document describes the additional properties required by raw Netlink
|
| H A D | specs.rst | 4 Netlink protocol specifications (in YAML)
7 Netlink protocol specifications are complete, machine readable descriptions of
8 Netlink protocols written in YAML. The goal of the specifications is to allow
9 separating Netlink parsing from user space logic and minimize the amount of
10 hand written Netlink code for each new family, command, attribute.
11 Netlink specs should be complete and not depend on any other spec
34 There are four schema levels for Netlink specs, from the simplest used
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
47 - ``netlink-raw`` - catch all schema supporting pre-Generic Netlink protocols
72 information on the Netlink specification properties that are only relevant to
[all …]
|
| H A D | index.rst | 4 Netlink Handbook
7 Netlink documentation for users.
|
| H A D | intro-specs.rst | 4 Using Netlink protocol specifications
7 This document is a quick starting guide for using Netlink protocol
14 developing Netlink related code. The tool is implemented in Python
15 and can use a YAML specification to issue Netlink requests
16 to the kernel. Only Generic Netlink is supported.
45 Python-pretty-printed. This is because some Netlink types can't
49 The spec and Netlink internals are factored out as a standalone
|
| H A D | genetlink-legacy.rst | 4 Netlink specification support for legacy Generic Netlink families
8 required to describe older Generic Netlink families which form
17 New Netlink families should use ``multi-attr`` to define arrays.
71 Netlink families should have instead defined this as a flat structure,
262 New Netlink families should never respond to a DO operation with multiple
|
| H A D | c-code-gen.rst | 4 Netlink spec C code generation
7 This document describes how Netlink specifications are used to render
|
| /openbmc/linux/tools/net/ynl/lib/ |
| H A D | ynl.py | 21 class Netlink: class
102 self.type = self._type & ~Netlink.NLA_TYPE_MASK
199 if self.nl_type == Netlink.NLMSG_ERROR:
203 elif self.nl_type == Netlink.NLMSG_DONE:
209 if self.nl_flags & Netlink.NLM_F_ACK_TLVS and extack_off:
213 if extack.type == Netlink.NLMSGERR_ATTR_MSG:
215 elif extack.type == Netlink.NLMSGERR_ATTR_MISS_TYPE:
217 elif extack.type == Netlink.NLMSGERR_ATTR_MISS_NEST:
219 elif extack.type == Netlink.NLMSGERR_ATTR_OFFS:
280 with socket.socket(socket.AF_NETLINK, socket.SOCK_RAW, Netlink.NETLINK_GENERIC) as sock:
[all …]
|
| H A D | __init__.py | 5 from .ynl import YnlFamily, Netlink
|
| /openbmc/linux/tools/net/ynl/ |
| H A D | cli.py | 9 from lib import YnlFamily, Netlink
23 const=Netlink.NLM_F_REPLACE)
25 const=Netlink.NLM_F_EXCL)
27 const=Netlink.NLM_F_CREATE)
29 const=Netlink.NLM_F_APPEND)
|
| /openbmc/openbmc/poky/meta/recipes-extended/libmnl/ |
| H A D | libmnl_1.0.5.bb | 1 SUMMARY = "Minimalistic user-space Netlink utility library"
2 DESCRIPTION = "Minimalistic user-space library oriented to Netlink developers, providing \
3 …functions for common tasks in parsing, validating, and constructing both the Netlink header and TL…
|
| /openbmc/linux/Documentation/networking/ |
| H A D | generic_netlink.rst | 4 Generic Netlink
7 A wiki document on how to use Generic Netlink can be found here:
|
| H A D | openvswitch.rst | 37 protocols that have become obsolete. Therefore, the Netlink interface
74 A flow key is passed over a Netlink socket as a sequence of Netlink
100 A wildcarded flow is described with two sequences of Netlink attributes
101 passed over the Netlink socket. A flow key, exactly as described above, and an
110 Support for the mask Netlink attribute is optional for both the kernel and user
|
| H A D | l2tp.rst | 92 Netlink API
99 L2TP uses `Generic Netlink`_ (GENL). Several commands are defined:
668 .. _Generic Netlink: generic_netlink.html
|
| H A D | filter.rst | 298 nla Netlink attribute of type X with offset A
299 nlan Nested Netlink attribute of type X with offset A
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | netlink.rst | 6 Netlink notes for kernel developers
58 Netlink specification
61 Documentation of the Netlink specification parts which are only relevant
|
| /openbmc/linux/net/netlink/ |
| H A D | Kconfig | 3 # Netlink Sockets
|
| /openbmc/linux/drivers/net/can/ |
| H A D | Kconfig | 53 bool "CAN device drivers with Netlink support"
57 standard library and provides features for the Netlink interface such
74 bit-rate specified via Netlink argument "bitrate" when the device
78 bit-timing parameters must be specified directly using the Netlink
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-filter/libnftnl/ |
| H A D | libnftnl_1.2.8.bb | 1 SUMMARY = "Library for low-level interaction with nftables Netlink's API over libmnl"
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/mdns/mdns/ |
| H A D | 0007-Mark-deleted-interfaces-as-being-changed.patch | 6 Netlink notification handling ignores messages for deleted links,
|
| /openbmc/phosphor-networkd/src/ |
| H A D | rtnetlink_server.cpp | 109 auto sock = socket(SocketDomain::Netlink, SocketType::Raw, in makeSock()
|
| H A D | netlink.cpp | 110 auto sock = socket(SocketDomain::Netlink, SocketType::Raw, in makeSocket()
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | autofs-mount-control.rst | 145 ioctl mechanism in favor of systems such as Netlink. An implementation
147 found to be inadequate, in this case. The Generic Netlink system was
148 used for this as raw Netlink would lead to a significant increase in
149 complexity. There's no question that the Generic Netlink system is an
164 mount at a time. A Generic Netlink implementation would exclude this
|
| /openbmc/docs/designs/ |
| H A D | ncsi-coredump.md | 94 Kernel |Netlink |MCTP
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | connector.rst | 102 Netlink itself is not a reliable protocol. That means that messages can
|