diff options
author | Hangbin Liu <liuhangbin@gmail.com> | 2024-04-04 14:31:12 +0800 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2024-04-05 22:32:49 -0700 |
commit | aa6485d813ad6d884d23e1e9cf3913be29a1f229 (patch) | |
tree | 673695b5e1b1500a49b331b4476d23c81fb6a77f /Documentation/userspace-api/netlink/genetlink-legacy.rst | |
parent | f410cbea9f3d2675b4c8e52af1d1985b11b387d1 (diff) | |
download | lwn-aa6485d813ad6d884d23e1e9cf3913be29a1f229.tar.gz lwn-aa6485d813ad6d884d23e1e9cf3913be29a1f229.zip |
ynl: rename array-nest to indexed-array
Some implementations, like bonding, has nest array with same attr type.
To support all kinds of entries under one nest array. As discussed[1],
let's rename array-nest to indexed-array, and assuming the value is
a nest by passing the type via sub-type.
[1] https://lore.kernel.org/netdev/20240312100105.16a59086@kernel.org/
Suggested-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
Link: https://lore.kernel.org/r/20240404063114.1221532-2-liuhangbin@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'Documentation/userspace-api/netlink/genetlink-legacy.rst')
-rw-r--r-- | Documentation/userspace-api/netlink/genetlink-legacy.rst | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/Documentation/userspace-api/netlink/genetlink-legacy.rst b/Documentation/userspace-api/netlink/genetlink-legacy.rst index 70a77387f6c4..54e8fb25e093 100644 --- a/Documentation/userspace-api/netlink/genetlink-legacy.rst +++ b/Documentation/userspace-api/netlink/genetlink-legacy.rst @@ -46,10 +46,16 @@ For reference the ``multi-attr`` array may look like this:: where ``ARRAY-ATTR`` is the array entry type. -array-nest -~~~~~~~~~~ +indexed-array +~~~~~~~~~~~~~ + +``indexed-array`` wraps the entire array in an extra attribute (hence +limiting its size to 64kB). The ``ENTRY`` nests are special and have the +index of the entry as their type instead of normal attribute type. -``array-nest`` creates the following structure:: +A ``sub-type`` is needed to describe what type in the ``ENTRY``. A ``nest`` +``sub-type`` means there are nest arrays in the ``ENTRY``, with the structure +looks like:: [SOME-OTHER-ATTR] [ARRAY-ATTR] |