€•Œsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œtranslations”Œ LanguagesNode”“”)”}”(hhh]”(hŒpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ//translations/zh_CN/userspace-api/netlink/specs”Œmodname”NŒ classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ//translations/zh_TW/userspace-api/netlink/specs”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ//translations/it_IT/userspace-api/netlink/specs”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ//translations/ja_JP/userspace-api/netlink/specs”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ//translations/ko_KR/userspace-api/netlink/specs”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ//translations/sp_SP/userspace-api/netlink/specs”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ%SPDX-License-Identifier: BSD-3-Clause”h]”hŒ%SPDX-License-Identifier: BSD-3-Clause”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h¡hhhžhhŸŒI/var/lib/git/docbuild/linux/Documentation/userspace-api/netlink/specs.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ)Netlink protocol specifications (in YAML)”h]”hŒ)Netlink protocol specifications (in YAML)”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ paragraph”“”)”}”(hXÏNetlink protocol specifications are complete, machine readable descriptions of Netlink protocols written in YAML. The goal of the specifications is to allow separating Netlink parsing from user space logic and minimize the amount of hand written Netlink code for each new family, command, attribute. Netlink specs should be complete and not depend on any other spec or C header file, making it easy to use in languages which can't include kernel headers directly.”h]”hXÑNetlink protocol specifications are complete, machine readable descriptions of Netlink protocols written in YAML. The goal of the specifications is to allow separating Netlink parsing from user space logic and minimize the amount of hand written Netlink code for each new family, command, attribute. Netlink specs should be complete and not depend on any other spec or C header file, making it easy to use in languages which canâ€™t include kernel headers directly.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒ2Internally kernel uses the YAML specs to generate:”h]”hŒ2Internally kernel uses the YAML specs to generate:”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhŒblock_quote”“”)”}”(hŒÊ- the C uAPI header - documentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/index.rst ` - policy tables for input attribute validation - operation tables ”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒthe C uAPI header”h]”hÊ)”}”(hhöh]”hŒthe C uAPI header”…””}”(hhøhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khhôubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhhïubhó)”}”(hŒqdocumentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/index.rst `”h]”hÊ)”}”(hj h]”(hŒ3documentation of the protocol as a ReST file - see ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ>:ref:`Documentation/networking/netlink_spec/index.rst `”h]”hŒinline”“”)”}”(hjh]”hŒ/Documentation/networking/netlink_spec/index.rst”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhjubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œuserspace-api/netlink/specs”Œ refdomain”j'Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆŒ reftarget”Œspecs”uh1hhŸh³h Khjubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhhïubhó)”}”(hŒ,policy tables for input attribute validation”h]”hÊ)”}”(hjIh]”hŒ,policy tables for input attribute validation”…””}”(hjKhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KhjGubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhhïubhó)”}”(hŒoperation tables ”h]”hÊ)”}”(hŒoperation tables”h]”hŒoperation tables”…””}”(hjbhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj^ubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhhïubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1híhŸh³h Khhéubah}”(h]”h ]”h"]”h$]”h&]”uh1hçhŸh³h Khh¶hžhubhÊ)”}”(hŒGYAML specifications can be found under ``Documentation/netlink/specs/``”h]”(hŒ'YAML specifications can be found under ”…””}”(hj„hžhhŸNh NubhŒliteral”“”)”}”(hŒ ``Documentation/netlink/specs/``”h]”hŒDocumentation/netlink/specs/”…””}”(hjŽhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒeThis document describes details of the schema. See :doc:`intro-specs` for a practical starting guide.”h]”(hŒ3This document describes details of the schema. See ”…””}”(hj¢hžhhŸNh Nubh)”}”(hŒ:doc:`intro-specs`”h]”j)”}”(hj¬h]”hŒintro-specs”…””}”(hj®hžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-doc”eh"]”h$]”h&]”uh1jhjªubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”j¸Œreftype”Œdoc”Œrefexplicit”‰Œrefwarn”ˆj9Œintro-specs”uh1hhŸh³h Khj¢ubhŒ for a practical starting guide.”…””}”(hj¢hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒ‡All specs must be licensed under ``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)`` to allow for easy adoption in user space code.”h]”(hŒ!All specs must be licensed under ”…””}”(hjÔhžhhŸNh Nubj)”}”(hŒ7``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)``”h]”hŒ3((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)”…””}”(hjÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÔubhŒ/ to allow for easy adoption in user space code.”…””}”(hjÔhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒCompatibility levels”h]”hŒCompatibility levels”…””}”(hj÷hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjôhžhhŸh³h K ubhÊ)”}”(hXPThere are four schema levels for Netlink specs, from the simplest used by new families to the most complex covering all the quirks of the old ones. Each next level inherits the attributes of the previous level, meaning that user capable of parsing more complex ``genetlink`` schemas is also compatible with simpler ones. The levels are:”h]”(hXThere are four schema levels for Netlink specs, from the simplest used by new families to the most complex covering all the quirks of the old ones. Each next level inherits the attributes of the previous level, meaning that user capable of parsing more complex ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒ> schemas is also compatible with simpler ones. The levels are:”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K"hjôhžhubhè)”}”(hXV- ``genetlink`` - most streamlined, should be used by all new families - ``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing customization of define and enum type and value names; this schema should be equivalent to ``genetlink`` for all implementations which don't interact directly with C uAPI headers - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of all old genetlink families, strange attribute formats, binary structures etc. - ``netlink-raw`` - catch all schema supporting pre-Generic Netlink protocols such as ``NETLINK_ROUTE`` ”h]”hî)”}”(hhh]”(hó)”}”(hŒD``genetlink`` - most streamlined, should be used by all new families”h]”hÊ)”}”(hj.h]”(j)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hj3hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0ubhŒ7 - most streamlined, should be used by all new families”…””}”(hj0hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K(hj,ubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj)ubhó)”}”(hŒý``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing customization of define and enum type and value names; this schema should be equivalent to ``genetlink`` for all implementations which don't interact directly with C uAPI headers”h]”hÊ)”}”(hŒý``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing customization of define and enum type and value names; this schema should be equivalent to ``genetlink`` for all implementations which don't interact directly with C uAPI headers”h]”(j)”}”(hŒ``genetlink-c``”h]”hŒgenetlink-c”…””}”(hjYhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjUubhŒ - superset of ”…””}”(hjUhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hjkhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjUubhŒ{ with extra attributes allowing customization of define and enum type and value names; this schema should be equivalent to ”…””}”(hjUhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hj}hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjUubhŒL for all implementations which donâ€™t interact directly with C uAPI headers”…””}”(hjUhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K)hjQubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj)ubhó)”}”(hŒš``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of all old genetlink families, strange attribute formats, binary structures etc.”h]”hÊ)”}”(hŒš``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of all old genetlink families, strange attribute formats, binary structures etc.”h]”(j)”}”(hŒ``genetlink-legacy``”h]”hŒgenetlink-legacy”…””}”(hj£hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjŸubhŒ† - Generic Netlink catch all schema supporting quirks of all old genetlink families, strange attribute formats, binary structures etc.”…””}”(hjŸhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K-hj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj)ubhó)”}”(hŒf``netlink-raw`` - catch all schema supporting pre-Generic Netlink protocols such as ``NETLINK_ROUTE`` ”h]”hÊ)”}”(hŒe``netlink-raw`` - catch all schema supporting pre-Generic Netlink protocols such as ``NETLINK_ROUTE``”h]”(j)”}”(hŒ``netlink-raw``”h]”hŒnetlink-raw”…””}”(hjÉhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÅubhŒE - catch all schema supporting pre-Generic Netlink protocols such as ”…””}”(hjÅhžhhŸNh Nubj)”}”(hŒ``NETLINK_ROUTE``”h]”hŒ NETLINK_ROUTE”…””}”(hjÛhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÅubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K/hjÁubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj)ubeh}”(h]”h ]”h"]”h$]”h&]”j|j}uh1híhŸh³h K(hj%ubah}”(h]”h ]”h"]”h$]”h&]”uh1hçhŸh³h K(hjôhžhubhÊ)”}”(hŒ`The definition of the schemas (in ``jsonschema``) can be found under ``Documentation/netlink/``.”h]”(hŒ"The definition of the schemas (in ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ``jsonschema``”h]”hŒ jsonschema”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒ) can be found under ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ``Documentation/netlink/``”h]”hŒDocumentation/netlink/”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒ.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K2hjôhžhubeh}”(h]”Œcompatibility-levels”ah ]”h"]”Œcompatibility levels”ah$]”h&]”uh1h´hh¶hžhhŸh³h K ubhµ)”}”(hhh]”(hº)”}”(hŒSchema structure”h]”hŒSchema structure”…””}”(hj>hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj;hžhhŸh³h K6ubhÊ)”}”(hŒ2YAML schema has the following conceptual sections:”h]”hŒ2YAML schema has the following conceptual sections:”…””}”(hjLhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K8hj;hžhubhè)”}”(hŒE- globals - definitions - attributes - operations - multicast groups ”h]”hî)”}”(hhh]”(hó)”}”(hŒglobals”h]”hÊ)”}”(hjch]”hŒglobals”…””}”(hjehžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K:hjaubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj^ubhó)”}”(hŒdefinitions”h]”hÊ)”}”(hjzh]”hŒdefinitions”…””}”(hj|hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K;hjxubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj^ubhó)”}”(hŒ attributes”h]”hÊ)”}”(hj‘h]”hŒ attributes”…””}”(hj“hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj½ubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj^ubeh}”(h]”h ]”h"]”h$]”h&]”j|j}uh1híhŸh³h K:hjZubah}”(h]”h ]”h"]”h$]”h&]”uh1hçhŸh³h K:hj;hžhubhÊ)”}”(hŒpMost properties in the schema accept (or in fact require) a ``doc`` sub-property documenting the defined object.”h]”(hŒ` for information on how C names are derived from name properties.”h]”(hŒBThe following sections describe the properties of the most modern ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒ" schema. See the documentation of ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ:doc:`genetlink-c `”h]”j)”}”(hjh]”hŒgenetlink-c”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-doc”eh"]”h$]”h&]”uh1jhjubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”j)Œreftype”Œdoc”Œrefexplicit”ˆŒrefwarn”ˆj9Œ c-code-gen”uh1hhŸh³h KChjubhŒA for information on how C names are derived from name properties.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KChj;hžhubhÊ)”}”(hŒÊSee also :ref:`Documentation/core-api/netlink.rst ` for information on the Netlink specification properties that are only relevant to the kernel space and not part of the user space API.”h]”(hŒ See also ”…””}”(hjEhžhhŸNh Nubh)”}”(hŒ::ref:`Documentation/core-api/netlink.rst `”h]”j)”}”(hjOh]”hŒ"Documentation/core-api/netlink.rst”…””}”(hjQhžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhjMubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”j[Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆj9Œkernel_netlink”uh1hhŸh³h KGhjEubhŒ‡ for information on the Netlink specification properties that are only relevant to the kernel space and not part of the user space API.”…””}”(hjEhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KGhj;hžhubeh}”(h]”Œschema-structure”ah ]”h"]”Œschema structure”ah$]”h&]”uh1h´hh¶hžhhŸh³h K6ubhµ)”}”(hhh]”(hº)”}”(hŒ genetlink”h]”hŒ genetlink”…””}”(hj‚hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h KLubhµ)”}”(hhh]”(hº)”}”(hŒGlobals”h]”hŒGlobals”…””}”(hj“hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h KOubhÊ)”}”(hŒ>Attributes listed directly at the root level of the spec file.”h]”hŒ>Attributes listed directly at the root level of the spec file.”…””}”(hj¡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KQhjhžhubhµ)”}”(hhh]”(hº)”}”(hŒname”h]”hŒname”…””}”(hj²hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¯hžhhŸh³h KTubhÊ)”}”(hŒoName of the family. Name identifies the family in a unique way, since the Family IDs are allocated dynamically.”h]”hŒoName of the family. Name identifies the family in a unique way, since the Family IDs are allocated dynamically.”…””}”(hjÀhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KVhj¯hžhubeh}”(h]”Œname”ah ]”h"]”h$]”Œname”ah&]”uh1h´hjhžhhŸh³h KTŒ referenced”Kubhµ)”}”(hhh]”(hº)”}”(hŒprotocol”h]”hŒprotocol”…””}”(hjÚhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj×hžhhŸh³h KZubhÊ)”}”(hŒkThe schema level, default is ``genetlink``, which is the only value allowed for new ``genetlink`` families.”h]”(hŒThe schema level, default is ”…””}”(hjèhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hjðhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjèubhŒ*, which is the only value allowed for new ”…””}”(hjèhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjèubhŒ families.”…””}”(hjèhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K\hj×hžhubeh}”(h]”Œprotocol”ah ]”h"]”Œprotocol”ah$]”h&]”uh1h´hjhžhhŸh³h KZubeh}”(h]”Œglobals”ah ]”h"]”Œglobals”ah$]”h&]”uh1h´hjhžhhŸh³h KOubhµ)”}”(hhh]”(hº)”}”(hŒdefinitions”h]”hŒdefinitions”…””}”(hj-hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj*hžhhŸh³h K`ubhÊ)”}”(hŒ'Array of type and constant definitions.”h]”hŒ'Array of type and constant definitions.”…””}”(hj;hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kbhj*hžhubhµ)”}”(hhh]”(hº)”}”(hŒname”h]”hŒname”…””}”(hjLhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjIhžhhŸh³h KeubhÊ)”}”(hŒName of the type / constant.”h]”hŒName of the type / constant.”…””}”(hjZhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KghjIhžhubeh}”(h]”Œid1”ah ]”h"]”h$]”jÔah&]”uh1h´hj*hžhhŸh³h KejÖKubhµ)”}”(hhh]”(hº)”}”(hŒtype”h]”hŒtype”…””}”(hjrhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjohžhhŸh³h KjubhÊ)”}”(hŒOne of the following types:”h]”hŒOne of the following types:”…””}”(hj€hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Klhjohžhubhè)”}”(hX- const - a single, standalone constant - enum - defines an integer enumeration, with values for each entry incrementing by 1, (e.g. 0, 1, 2, 3) - flags - defines an integer enumeration, with values for each entry occupying a bit, starting from bit 0, (e.g. 1, 2, 4, 8) ”h]”hî)”}”(hhh]”(hó)”}”(hŒ%const - a single, standalone constant”h]”hÊ)”}”(hj—h]”hŒ%const - a single, standalone constant”…””}”(hj™hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Knhj•ubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj’ubhó)”}”(hŒfenum - defines an integer enumeration, with values for each entry incrementing by 1, (e.g. 0, 1, 2, 3)”h]”hÊ)”}”(hŒfenum - defines an integer enumeration, with values for each entry incrementing by 1, (e.g. 0, 1, 2, 3)”h]”hŒfenum - defines an integer enumeration, with values for each entry incrementing by 1, (e.g. 0, 1, 2, 3)”…””}”(hj°hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kohj¬ubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj’ubhó)”}”(hŒ{flags - defines an integer enumeration, with values for each entry occupying a bit, starting from bit 0, (e.g. 1, 2, 4, 8) ”h]”hÊ)”}”(hŒzflags - defines an integer enumeration, with values for each entry occupying a bit, starting from bit 0, (e.g. 1, 2, 4, 8)”h]”hŒzflags - defines an integer enumeration, with values for each entry occupying a bit, starting from bit 0, (e.g. 1, 2, 4, 8)”…””}”(hjÈhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KqhjÄubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhj’ubeh}”(h]”h ]”h"]”h$]”h&]”j|j}uh1híhŸh³h KnhjŽubah}”(h]”h ]”h"]”h$]”h&]”uh1hçhŸh³h Knhjohžhubeh}”(h]”Œtype”ah ]”h"]”h$]”Œtype”ah&]”uh1h´hj*hžhhŸh³h KjjÖKubhµ)”}”(hhh]”(hº)”}”(hŒvalue”h]”hŒvalue”…””}”(hjóhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjðhžhhŸh³h KuubhÊ)”}”(hŒThe value for the ``const``.”h]”(hŒThe value for the ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ ``const``”h]”hŒconst”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒ.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kwhjðhžhubeh}”(h]”Œvalue”ah ]”h"]”h$]”Œvalue”ah&]”uh1h´hj*hžhhŸh³h KujÖKubhµ)”}”(hhh]”(hº)”}”(hŒvalue-start”h]”hŒvalue-start”…””}”(hj,hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj)hžhhŸh³h KzubhÊ)”}”(hŒÞThe first value for ``enum`` and ``flags``, allows overriding the default start value of ``0`` (for ``enum``) and starting bit (for ``flags``). For ``flags`` ``value-start`` selects the starting bit, not the shifted value.”h]”(hŒThe first value for ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hjBhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ and ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hjThžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ/, allows overriding the default start value of ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ``0``”h]”hŒ0”…””}”(hjfhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ (for ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hjxhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ) and starting bit (for ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hjŠhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ). For ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hjœhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ ”…””}”(hj:hžhhŸNh Nubj)”}”(hŒ``value-start``”h]”hŒvalue-start”…””}”(hj®hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj:ubhŒ1 selects the starting bit, not the shifted value.”…””}”(hj:hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K|hj)hžhubhÊ)”}”(hŒ&Sparse enumerations are not supported.”h]”hŒ&Sparse enumerations are not supported.”…””}”(hjÆhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K€hj)hžhubeh}”(h]”Œvalue-start”ah ]”h"]”Œvalue-start”ah$]”h&]”uh1h´hj*hžhhŸh³h Kzubhµ)”}”(hhh]”(hº)”}”(hŒentries”h]”hŒentries”…””}”(hjßhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÜhžhhŸh³h KƒubhÊ)”}”(hŒ9Array of names of the entries for ``enum`` and ``flags``.”h]”(hŒ"Array of names of the entries for ”…””}”(hjíhžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hjõhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjíubhŒ and ”…””}”(hjíhžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjíubhŒ.”…””}”(hjíhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K…hjÜhžhubeh}”(h]”Œentries”ah ]”h"]”Œentries”ah$]”h&]”uh1h´hj*hžhhŸh³h Kƒubhµ)”}”(hhh]”(hº)”}”(hŒheader”h]”hŒheader”…””}”(hj*hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj'hžhhŸh³h KˆubhÊ)”}”(hX For C-compatible languages, header which already defines this value. In case the definition is shared by multiple families (e.g. ``IFNAMSIZ``) code generators for C-compatible languages may prefer to add an appropriate include instead of rendering a new definition.”h]”(hŒFor C-compatible languages, header which already defines this value. In case the definition is shared by multiple families (e.g. ”…””}”(hj8hžhhŸNh Nubj)”}”(hŒ``IFNAMSIZ``”h]”hŒIFNAMSIZ”…””}”(hj@hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj8ubhŒ|) code generators for C-compatible languages may prefer to add an appropriate include instead of rendering a new definition.”…””}”(hj8hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KŠhj'hžhubeh}”(h]”Œheader”ah ]”h"]”Œheader”ah$]”h&]”uh1h´hj*hžhhŸh³h Kˆubeh}”(h]”Œdefinitions”ah ]”h"]”Œdefinitions”ah$]”h&]”uh1h´hjhžhhŸh³h K`ubhµ)”}”(hhh]”(hº)”}”(hŒattribute-sets”h]”hŒattribute-sets”…””}”(hjkhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhhžhhŸh³h KubhÊ)”}”(hŒÕThis property contains information about netlink attributes of the family. All families have at least one attribute set, most have multiple. ``attribute-sets`` is an array, with each entry describing a single set.”h]”(hŒThis property contains information about netlink attributes of the family. All families have at least one attribute set, most have multiple. ”…””}”(hjyhžhhŸNh Nubj)”}”(hŒ``attribute-sets``”h]”hŒattribute-sets”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjyubhŒ6 is an array, with each entry describing a single set.”…””}”(hjyhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K’hjhhžhubhÊ)”}”(hXfNote that the spec is "flattened" and is not meant to visually resemble the format of the netlink messages (unlike certain ad-hoc documentation formats seen in kernel comments). In the spec subordinate attribute sets are not defined inline as a nest, but defined in a separate attribute set referred to with a ``nested-attributes`` property of the container.”h]”(hX:Note that the spec is â€œflattenedâ€ and is not meant to visually resemble the format of the netlink messages (unlike certain ad-hoc documentation formats seen in kernel comments). In the spec subordinate attribute sets are not defined inline as a nest, but defined in a separate attribute set referred to with a ”…””}”(hj™hžhhŸNh Nubj)”}”(hŒ``nested-attributes``”h]”hŒnested-attributes”…””}”(hj¡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj™ubhŒ property of the container.”…””}”(hj™hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K–hjhhžhubhÊ)”}”(hXASpec may also contain fractional sets - sets which contain a ``subset-of`` property. Such sets describe a section of a full set, allowing narrowing down which attributes are allowed in a nest or refining the validation criteria. Fractional sets can only be used in nests. They are not rendered to the uAPI in any fashion.”h]”(hŒ=Spec may also contain fractional sets - sets which contain a ”…””}”(hj¹hžhhŸNh Nubj)”}”(hŒ ``subset-of``”h]”hŒ subset-of”…””}”(hjÁhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj¹ubhŒ÷ property. Such sets describe a section of a full set, allowing narrowing down which attributes are allowed in a nest or refining the validation criteria. Fractional sets can only be used in nests. They are not rendered to the uAPI in any fashion.”…””}”(hj¹hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kœhjhhžhubhµ)”}”(hhh]”(hº)”}”(hŒname”h]”hŒname”…””}”(hjÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÙhžhhŸh³h K£ubhÊ)”}”(hŒjUniquely identifies the attribute set, operations and nested attributes refer to the sets by the ``name``.”h]”(hŒaUniquely identifies the attribute set, operations and nested attributes refer to the sets by the ”…””}”(hjêhžhhŸNh Nubj)”}”(hŒ``name``”h]”hŒname”…””}”(hjòhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjêubhŒ.”…””}”(hjêhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K¥hjÙhžhubeh}”(h]”Œid2”ah ]”h"]”h$]”Œname”ah&]”uh1h´hjhhžhhŸh³h K£jÖKubhµ)”}”(hhh]”(hº)”}”(hŒ subset-of”h]”hŒ subset-of”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h K©ubhÊ)”}”(hX%Re-defines a portion of another set (a fractional set). Allows narrowing down fields and changing validation criteria or even types of attributes depending on the nest in which they are contained. The ``value`` of each attribute in the fractional set is implicitly the same as in the main set.”h]”(hŒÉRe-defines a portion of another set (a fractional set). Allows narrowing down fields and changing validation criteria or even types of attributes depending on the nest in which they are contained. The ”…””}”(hj#hžhhŸNh Nubj)”}”(hŒ ``value``”h]”hŒvalue”…””}”(hj+hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj#ubhŒS of each attribute in the fractional set is implicitly the same as in the main set.”…””}”(hj#hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K«hjhžhubeh}”(h]”Œ subset-of”ah ]”h"]”Œ subset-of”ah$]”h&]”uh1h´hjhhžhhŸh³h K©ubhµ)”}”(hhh]”(hº)”}”(hŒ attributes”h]”hŒ attributes”…””}”(hjNhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjKhžhhŸh³h K²ubhÊ)”}”(hŒList of attributes in the set.”h]”hŒList of attributes in the set.”…””}”(hj\hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K´hjKhžhubhŒtarget”“”)”}”(hŒ.. _attribute_properties:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œattribute-properties”uh1jjh K¶hjKhžhhŸh³ubeh}”(h]”Œ attributes”ah ]”h"]”Œ attributes”ah$]”h&]”uh1h´hjhhžhhŸh³h K²ubeh}”(h]”Œattribute-sets”ah ]”h"]”Œattribute-sets”ah$]”h&]”uh1h´hjhžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒAttribute properties”h]”hŒAttribute properties”…””}”(hj‹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjˆhžhhŸh³h K¹ubhµ)”}”(hhh]”(hº)”}”(hŒname”h]”hŒname”…””}”(hjœhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj™hžhhŸh³h K¼ubhÊ)”}”(hŒ0Identifies the attribute, unique within the set.”h]”hŒ0Identifies the attribute, unique within the set.”…””}”(hjªhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K¾hj™hžhubeh}”(h]”Œid4”ah ]”h"]”h$]”Œname”ah&]”uh1h´hjˆhžhhŸh³h K¼jÖKubhµ)”}”(hhh]”(hº)”}”(hŒtype”h]”hŒtype”…””}”(hjÃhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÀhžhhŸh³h KÁubhÊ)”}”(hŒ.Netlink attribute type, see :ref:`attr_types`.”h]”(hŒNetlink attribute type, see ”…””}”(hjÑhžhhŸNh Nubh)”}”(hŒ:ref:`attr_types`”h]”j)”}”(hjÛh]”hŒ attr_types”…””}”(hjÝhžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhjÙubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”jçŒreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj9Œ attr_types”uh1hhŸh³h KÃhjÑubhŒ.”…””}”(hjÑhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÃhjÀhžhubjk)”}”(hŒ.. _assign_val:”h]”h}”(h]”h ]”h"]”h$]”h&]”jvŒ assign-val”uh1jjh KÅhjÀhžhhŸh³ubeh}”(h]”Œid5”ah ]”h"]”h$]”jîah&]”uh1h´hjˆhžhhŸh³h KÁjÖKubhµ)”}”(hhh]”(hº)”}”(hŒvalue”h]”hŒvalue”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj hžhhŸh³h KÈubhÊ)”}”(hŒýNumerical attribute ID, used in serialized Netlink messages. The ``value`` property can be skipped, in which case the attribute ID will be the value of the previous attribute plus one (recursively) and ``1`` for the first attribute in the attribute set.”h]”(hŒANumerical attribute ID, used in serialized Netlink messages. The ”…””}”(hj& hžhhŸNh Nubj)”}”(hŒ ``value``”h]”hŒvalue”…””}”(hj. hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj& ubhŒ€ property can be skipped, in which case the attribute ID will be the value of the previous attribute plus one (recursively) and ”…””}”(hj& hžhhŸNh Nubj)”}”(hŒ``1``”h]”hŒ1”…””}”(hj@ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj& ubhŒ. for the first attribute in the attribute set.”…””}”(hj& hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÊhj hžhubhÊ)”}”(hŒñAttributes (and operations) use ``1`` as the default value for the first entry (unlike enums in definitions which start from ``0``) because entry ``0`` is almost always reserved as undefined. Spec can explicitly set value to ``0`` if needed.”h]”(hŒ Attributes (and operations) use ”…””}”(hjX hžhhŸNh Nubj)”}”(hŒ``1``”h]”hŒ1”…””}”(hj` hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjX ubhŒX as the default value for the first entry (unlike enums in definitions which start from ”…””}”(hjX hžhhŸNh Nubj)”}”(hŒ``0``”h]”hŒ0”…””}”(hjr hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjX ubhŒ) because entry ”…””}”(hjX hžhhŸNh Nubj)”}”(hŒ``0``”h]”hŒ0”…””}”(hj„ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjX ubhŒJ is almost always reserved as undefined. Spec can explicitly set value to ”…””}”(hjX hžhhŸNh Nubj)”}”(hŒ``0``”h]”hŒ0”…””}”(hj– hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjX ubhŒ if needed.”…””}”(hjX hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÏhj hžhubhÊ)”}”(hŒYNote that the ``value`` of an attribute is defined only in its main set (not in subsets).”h]”(hŒNote that the ”…””}”(hj® hžhhŸNh Nubj)”}”(hŒ ``value``”h]”hŒvalue”…””}”(hj¶ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj® ubhŒB of an attribute is defined only in its main set (not in subsets).”…””}”(hj® hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÔhj hžhubeh}”(h]”(j Œid6”eh ]”h"]”Œ assign_val”ah$]”j'ah&]”uh1h´hjˆhžhhŸh³h KÈjÖKŒexpect_referenced_by_name”}”jÓ j sŒexpect_referenced_by_id”}”j j subhµ)”}”(hhh]”(hº)”}”(hŒenum”h]”hŒenum”…””}”(hjÝ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÚ hžhhŸh³h KØubhÊ)”}”(hŒ}For integer types specifies that values in the attribute belong to an ``enum`` or ``flags`` from the ``definitions`` section.”h]”(hŒFFor integer types specifies that values in the attribute belong to an ”…””}”(hjë hžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hjó hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjë ubhŒ or ”…””}”(hjë hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjë ubhŒ from the ”…””}”(hjë hžhhŸNh Nubj)”}”(hŒ``definitions``”h]”hŒdefinitions”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjë ubhŒ section.”…””}”(hjë hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÚhjÚ hžhubeh}”(h]”Œenum”ah ]”h"]”Œenum”ah$]”h&]”uh1h´hjˆhžhhŸh³h KØubhµ)”}”(hhh]”(hº)”}”(hŒ enum-as-flags”h]”hŒ enum-as-flags”…””}”(hj: hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj7 hžhhŸh³h KÞubhÊ)”}”(hŒëTreat ``enum`` as ``flags`` regardless of its type in ``definitions``. When both ``enum`` and ``flags`` forms are needed ``definitions`` should contain an ``enum`` and attributes which need the ``flags`` form should use this attribute.”h]”(hŒTreat ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hjP hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ as ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hjb hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ regardless of its type in ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ``definitions``”h]”hŒdefinitions”…””}”(hjt hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ. When both ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hj† hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ and ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hj˜ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ forms are needed ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ``definitions``”h]”hŒdefinitions”…””}”(hjª hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ should contain an ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ``enum``”h]”hŒenum”…””}”(hj¼ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ and attributes which need the ”…””}”(hjH hžhhŸNh Nubj)”}”(hŒ ``flags``”h]”hŒflags”…””}”(hjÎ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjH ubhŒ form should use this attribute.”…””}”(hjH hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kàhj7 hžhubeh}”(h]”Œ enum-as-flags”ah ]”h"]”Œ enum-as-flags”ah$]”h&]”uh1h´hjˆhžhhŸh³h KÞubhµ)”}”(hhh]”(hº)”}”(hŒnested-attributes”h]”hŒnested-attributes”…””}”(hjñ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjî hžhhŸh³h KæubhÊ)”}”(hŒIdentifies the attribute space for attributes nested within given attribute. Only valid for complex attributes which may have sub-attributes.”h]”hŒIdentifies the attribute space for attributes nested within given attribute. Only valid for complex attributes which may have sub-attributes.”…””}”(hjÿ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kèhjî hžhubeh}”(h]”Œnested-attributes”ah ]”h"]”Œnested-attributes”ah$]”h&]”uh1h´hjˆhžhhŸh³h Kæubhµ)”}”(hhh]”(hº)”}”(hŒmulti-attr (arrays)”h]”hŒmulti-attr (arrays)”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h KìubhÊ)”}”(hŒ¯Boolean property signifying that the attribute may be present multiple times. Allowing an attribute to repeat is the recommended way of implementing arrays (no extra nesting).”h]”hŒ¯Boolean property signifying that the attribute may be present multiple times. Allowing an attribute to repeat is the recommended way of implementing arrays (no extra nesting).”…””}”(hj&hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kîhjhžhubeh}”(h]”Œmulti-attr-arrays”ah ]”h"]”Œmulti-attr (arrays)”ah$]”h&]”uh1h´hjˆhžhhŸh³h Kìubhµ)”}”(hhh]”(hº)”}”(hŒ byte-order”h]”hŒ byte-order”…””}”(hj?hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj<hžhhŸh³h KóubhÊ)”}”(hŒWFor integer types specifies attribute byte order - ``little-endian`` or ``big-endian``.”h]”(hŒ3For integer types specifies attribute byte order - ”…””}”(hjMhžhhŸNh Nubj)”}”(hŒ``little-endian``”h]”hŒ little-endian”…””}”(hjUhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjMubhŒ or ”…””}”(hjMhžhhŸNh Nubj)”}”(hŒ``big-endian``”h]”hŒ big-endian”…””}”(hjghžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjMubhŒ.”…””}”(hjMhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kõhj<hžhubeh}”(h]”Œ byte-order”ah ]”h"]”Œ byte-order”ah$]”h&]”uh1h´hjˆhžhhŸh³h Kóubhµ)”}”(hhh]”(hº)”}”(hŒchecks”h]”hŒchecks”…””}”(hjŠhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj‡hžhhŸh³h KùubhÊ)”}”(hŒÈInput validation constraints used by the kernel. User space should query the policy of the running kernel using Generic Netlink introspection, rather than depend on what is specified in the spec file.”h]”hŒÈInput validation constraints used by the kernel. User space should query the policy of the running kernel using Generic Netlink introspection, rather than depend on what is specified in the spec file.”…””}”(hj˜hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kûhj‡hžhubhÊ)”}”(hŒ‡The validation policy in the kernel is formed by combining the type definition (``type`` and ``nested-attributes``) and the ``checks``.”h]”(hŒPThe validation policy in the kernel is formed by combining the type definition (”…””}”(hj¦hžhhŸNh Nubj)”}”(hŒ``type``”h]”hŒtype”…””}”(hj®hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj¦ubhŒ and ”…””}”(hj¦hžhhŸNh Nubj)”}”(hŒ``nested-attributes``”h]”hŒnested-attributes”…””}”(hjÀhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj¦ubhŒ ) and the ”…””}”(hj¦hžhhŸNh Nubj)”}”(hŒ ``checks``”h]”hŒchecks”…””}”(hjÒhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj¦ubhŒ.”…””}”(hj¦hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kÿhj‡hžhubeh}”(h]”Œchecks”ah ]”h"]”Œchecks”ah$]”h&]”uh1h´hjˆhžhhŸh³h Kùubhµ)”}”(hhh]”(hº)”}”(hŒsub-type”h]”hŒsub-type”…””}”(hjõhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjòhžhhŸh³h MubhÊ)”}”(hX’Legacy families have special ways of expressing arrays. ``sub-type`` can be used to define the type of array members in case array members are not fully defined as attributes (in a bona fide attribute space). For instance a C array of u32 values can be specified with ``type: binary`` and ``sub-type: u32``. Binary types and legacy array formats are described in more detail in :doc:`genetlink-legacy`.”h]”(hŒ8Legacy families have special ways of expressing arrays. ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ``sub-type``”h]”hŒsub-type”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒÈ can be used to define the type of array members in case array members are not fully defined as attributes (in a bona fide attribute space). For instance a C array of u32 values can be specified with ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ``type: binary``”h]”hŒtype: binary”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒ and ”…””}”(hjhžhhŸNh Nubj)”}”(hŒ``sub-type: u32``”h]”hŒ sub-type: u32”…””}”(hj/hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjubhŒH. Binary types and legacy array formats are described in more detail in ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ:doc:`genetlink-legacy`”h]”j)”}”(hjCh]”hŒgenetlink-legacy”…””}”(hjEhžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-doc”eh"]”h$]”h&]”uh1jhjAubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”jOŒreftype”Œdoc”Œrefexplicit”‰Œrefwarn”ˆj9Œgenetlink-legacy”uh1hhŸh³h MhjubhŒ.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mhjòhžhubeh}”(h]”Œsub-type”ah ]”h"]”Œsub-type”ah$]”h&]”uh1h´hjˆhžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒdisplay-hint”h]”hŒdisplay-hint”…””}”(hjvhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjshžhhŸh³h M ubhÊ)”}”(hŒÛOptional format indicator that is intended only for choosing the right formatting mechanism when displaying values of this type. Currently supported hints are ``hex``, ``mac``, ``fddi``, ``ipv4``, ``ipv6`` and ``uuid``.”h]”(hŒŸOptional format indicator that is intended only for choosing the right formatting mechanism when displaying values of this type. Currently supported hints are ”…””}”(hj„hžhhŸNh Nubj)”}”(hŒ``hex``”h]”hŒhex”…””}”(hjŒhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubhŒ, ”…””}”(hj„hžhhŸNh Nubj)”}”(hŒ``mac``”h]”hŒmac”…””}”(hjžhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubhŒ, ”…””}”hj„sbj)”}”(hŒ``fddi``”h]”hŒfddi”…””}”(hj°hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubhŒ, ”…””}”hj„sbj)”}”(hŒ``ipv4``”h]”hŒipv4”…””}”(hjÂhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubhŒ, ”…””}”hj„sbj)”}”(hŒ``ipv6``”h]”hŒipv6”…””}”(hjÔhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubhŒ and ”…””}”(hj„hžhhŸNh Nubj)”}”(hŒ``uuid``”h]”hŒuuid”…””}”(hjæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj„ubhŒ.”…””}”(hj„hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mhjshžhubeh}”(h]”Œdisplay-hint”ah ]”h"]”Œdisplay-hint”ah$]”h&]”uh1h´hjˆhžhhŸh³h M ubeh}”(h]”(jwŒid3”eh ]”h"]”(Œattribute properties”Œattribute_properties”eh$]”h&]”uh1h´hjhžhhŸh³h K¹jÖ }”j jlsjØ }”jwjlsubhµ)”}”(hhh]”(hº)”}”(hŒ operations”h]”hŒ operations”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj hžhhŸh³h MubhÊ)”}”(hŒ¦This section describes messages passed between the kernel and the user space. There are three types of entries in this section - operations, notifications and events.”h]”hŒ¦This section describes messages passed between the kernel and the user space. There are three types of entries in this section - operations, notifications and events.”…””}”(hj" hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mhj hžhubhÊ)”}”(hXùOperations describe the most common request - response communication. User sends a request and kernel replies. Each operation may contain any combination of the two modes familiar to netlink users - ``do`` and ``dump``. ``do`` and ``dump`` in turn contain a combination of ``request`` and ``response`` properties. If no explicit message with attributes is passed in a given direction (e.g. a ``dump`` which does not accept filter, or a ``do`` of a SET operation to which the kernel responds with just the netlink error code) ``request`` or ``response`` section can be skipped. ``request`` and ``response`` sections list the attributes allowed in a message. The list contains only the names of attributes from a set referred to by the ``attribute-set`` property.”h]”(hŒÇOperations describe the most common request - response communication. User sends a request and kernel replies. Each operation may contain any combination of the two modes familiar to netlink users - ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``do``”h]”hŒdo”…””}”(hj8 hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ and ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``dump``”h]”hŒdump”…””}”(hjJ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ. ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``do``”h]”hŒdo”…””}”(hj\ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ and ”…””}”hj0 sbj)”}”(hŒ``dump``”h]”hŒdump”…””}”(hjn hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ" in turn contain a combination of ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``request``”h]”hŒrequest”…””}”(hj€ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ and ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``response``”h]”hŒresponse”…””}”(hj’ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ[ properties. If no explicit message with attributes is passed in a given direction (e.g. a ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``dump``”h]”hŒdump”…””}”(hj¤ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ$ which does not accept filter, or a ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``do``”h]”hŒdo”…””}”(hj¶ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒS of a SET operation to which the kernel responds with just the netlink error code) ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``request``”h]”hŒrequest”…””}”(hjÈ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ or ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``response``”h]”hŒresponse”…””}”(hjÚ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ section can be skipped. ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``request``”h]”hŒrequest”…””}”(hjì hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ and ”…””}”hj0 sbj)”}”(hŒ``response``”h]”hŒresponse”…””}”(hjþ hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ sections list the attributes allowed in a message. The list contains only the names of attributes from a set referred to by the ”…””}”(hj0 hžhhŸNh Nubj)”}”(hŒ``attribute-set``”h]”hŒ attribute-set”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj0 ubhŒ property.”…””}”(hj0 hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mhj hžhubhÊ)”}”(hX™Notifications and events both refer to the asynchronous messages sent by the kernel to members of a multicast group. The difference between the two is that a notification shares its contents with a GET operation (the name of the GET operation is specified in the ``notify`` property). This arrangement is commonly used for notifications about objects where the notification carries the full object definition.”h]”(hXNotifications and events both refer to the asynchronous messages sent by the kernel to members of a multicast group. The difference between the two is that a notification shares its contents with a GET operation (the name of the GET operation is specified in the ”…””}”(hj(hžhhŸNh Nubj)”}”(hŒ ``notify``”h]”hŒnotify”…””}”(hj0hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj(ubhŒˆ property). This arrangement is commonly used for notifications about objects where the notification carries the full object definition.”…””}”(hj(hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M&hj hžhubhÊ)”}”(hXGEvents are more focused and carry only a subset of information rather than full object state (a made up example would be a link state change event with just the interface name and the new link state). Events contain the ``event`` property. Events are considered less idiomatic for netlink and notifications should be preferred.”h]”(hŒÜEvents are more focused and carry only a subset of information rather than full object state (a made up example would be a link state change event with just the interface name and the new link state). Events contain the ”…””}”(hjHhžhhŸNh Nubj)”}”(hŒ ``event``”h]”hŒevent”…””}”(hjPhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjHubhŒb property. Events are considered less idiomatic for netlink and notifications should be preferred.”…””}”(hjHhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M-hj hžhubhµ)”}”(hhh]”(hº)”}”(hŒlist”h]”hŒlist”…””}”(hjkhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhhžhhŸh³h M4ubhÊ)”}”(hŒgThe only property of ``operations`` for ``genetlink``, holds the list of operations, notifications etc.”h]”(hŒThe only property of ”…””}”(hjyhžhhŸNh Nubj)”}”(hŒ``operations``”h]”hŒ operations”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjyubhŒ for ”…””}”(hjyhžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hj“hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjyubhŒ2, holds the list of operations, notifications etc.”…””}”(hjyhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M6hjhhžhubeh}”(h]”Œlist”ah ]”h"]”h$]”Œlist”ah&]”uh1h´hj hžhhŸh³h M4jÖKubeh}”(h]”Œ operations”ah ]”h"]”Œ operations”ah$]”h&]”uh1h´hjhžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒOperation properties”h]”hŒOperation properties”…””}”(hj¾hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj»hžhhŸh³h M:ubhµ)”}”(hhh]”(hº)”}”(hŒname”h]”hŒname”…””}”(hjÏhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÌhžhhŸh³h M=ubhÊ)”}”(hŒIdentifies the operation.”h]”hŒIdentifies the operation.”…””}”(hjÝhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M?hjÌhžhubeh}”(h]”Œid7”ah ]”h"]”h$]”Œname”ah&]”uh1h´hj»hžhhŸh³h M=jÖKubhµ)”}”(hhh]”(hº)”}”(hŒvalue”h]”hŒvalue”…””}”(hjöhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjóhžhhŸh³h MBubhÊ)”}”(hŒŒNumerical message ID, used in serialized Netlink messages. The same enumeration rules are applied as to :ref:`attribute values`.”h]”(hŒhNumerical message ID, used in serialized Netlink messages. The same enumeration rules are applied as to ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ#:ref:`attribute values`”h]”j)”}”(hjh]”hŒattribute values”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhjubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”jŒreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆj9Œ assign_val”uh1hhŸh³h MDhjubhŒ.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h MDhjóhžhubeh}”(h]”Œid8”ah ]”h"]”h$]”Œvalue”ah&]”uh1h´hj»hžhhŸh³h MBjÖKubhµ)”}”(hhh]”(hº)”}”(hŒ attribute-set”h]”hŒ attribute-set”…””}”(hjAhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj>hžhhŸh³h MIubhÊ)”}”(hŒ9Specifies the attribute set contained within the message.”h]”hŒ9Specifies the attribute set contained within the message.”…””}”(hjOhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h MKhj>hžhubeh}”(h]”Œ attribute-set”ah ]”h"]”Œ attribute-set”ah$]”h&]”uh1h´hj»hžhhŸh³h MIubhµ)”}”(hhh]”(hº)”}”(hŒdo”h]”hŒdo”…””}”(hjhhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjehžhhŸh³h MNubhÊ)”}”(hŒ‹Specification for the ``doit`` request. Should contain ``request``, ``reply`` or both of these properties, each holding a :ref:`attr_list`.”h]”(hŒSpecification for the ”…””}”(hjvhžhhŸNh Nubj)”}”(hŒ``doit``”h]”hŒdoit”…””}”(hj~hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjvubhŒ request. Should contain ”…””}”(hjvhžhhŸNh Nubj)”}”(hŒ``request``”h]”hŒrequest”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjvubhŒ, ”…””}”(hjvhžhhŸNh Nubj)”}”(hŒ ``reply``”h]”hŒreply”…””}”(hj¢hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjvubhŒ- or both of these properties, each holding a ”…””}”(hjvhžhhŸNh Nubh)”}”(hŒ:ref:`attr_list`”h]”j)”}”(hj¶h]”hŒ attr_list”…””}”(hj¸hžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhj´ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”jÂŒreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj9Œ attr_list”uh1hhŸh³h MPhjvubhŒ.”…””}”(hjvhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h MPhjehžhubeh}”(h]”Œdo”ah ]”h"]”Œdo”ah$]”h&]”uh1h´hj»hžhhŸh³h MNubhµ)”}”(hhh]”(hº)”}”(hŒdump”h]”hŒdump”…””}”(hjéhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjæhžhhŸh³h MTubhÊ)”}”(hŒSpecification for the ``dumpit`` request. Should contain ``request``, ``reply`` or both of these properties, each holding a :ref:`attr_list`.”h]”(hŒSpecification for the ”…””}”(hj÷hžhhŸNh Nubj)”}”(hŒ ``dumpit``”h]”hŒdumpit”…””}”(hjÿhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj÷ubhŒ request. Should contain ”…””}”(hj÷hžhhŸNh Nubj)”}”(hŒ``request``”h]”hŒrequest”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj÷ubhŒ, ”…””}”(hj÷hžhhŸNh Nubj)”}”(hŒ ``reply``”h]”hŒreply”…””}”(hj#hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj÷ubhŒ- or both of these properties, each holding a ”…””}”(hj÷hžhhŸNh Nubh)”}”(hŒ:ref:`attr_list`”h]”j)”}”(hj7h]”hŒ attr_list”…””}”(hj9hžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhj5ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”jCŒreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj9Œ attr_list”uh1hhŸh³h MVhj÷ubhŒ.”…””}”(hj÷hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h MVhjæhžhubeh}”(h]”Œdump”ah ]”h"]”Œdump”ah$]”h&]”uh1h´hj»hžhhŸh³h MTubhµ)”}”(hhh]”(hº)”}”(hŒnotify”h]”hŒnotify”…””}”(hjjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjghžhhŸh³h MZubhÊ)”}”(hŒÁDesignates the message as a notification. Contains the name of the operation (possibly the same as the operation holding this property) which shares the contents with the notification (``do``).”h]”(hŒ¹Designates the message as a notification. Contains the name of the operation (possibly the same as the operation holding this property) which shares the contents with the notification (”…””}”(hjxhžhhŸNh Nubj)”}”(hŒ``do``”h]”hŒdo”…””}”(hj€hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjxubhŒ).”…””}”(hjxhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M\hjghžhubeh}”(h]”Œnotify”ah ]”h"]”Œnotify”ah$]”h&]”uh1h´hj»hžhhŸh³h MZubhµ)”}”(hhh]”(hº)”}”(hŒevent”h]”hŒevent”…””}”(hj£hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj hžhhŸh³h MaubhÊ)”}”(hŒ}Specification of attributes in the event, holds a :ref:`attr_list`. ``event`` property is mutually exclusive with ``notify``.”h]”(hŒ2Specification of attributes in the event, holds a ”…””}”(hj±hžhhŸNh Nubh)”}”(hŒ:ref:`attr_list`”h]”j)”}”(hj»h]”hŒ attr_list”…””}”(hj½hžhhŸNh Nubah}”(h]”h ]”(j&Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jhj¹ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j3Œ refdomain”jÇŒreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj9Œ attr_list”uh1hhŸh³h Mchj±ubhŒ. ”…””}”(hj±hžhhŸNh Nubj)”}”(hŒ ``event``”h]”hŒevent”…””}”(hjÝhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj±ubhŒ% property is mutually exclusive with ”…””}”(hj±hžhhŸNh Nubj)”}”(hŒ ``notify``”h]”hŒnotify”…””}”(hjïhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj±ubhŒ.”…””}”(hj±hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mchj hžhubeh}”(h]”Œevent”ah ]”h"]”Œevent”ah$]”h&]”uh1h´hj»hžhhŸh³h Maubhµ)”}”(hhh]”(hº)”}”(hŒmcgrp”h]”hŒmcgrp”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h MgubhÊ)”}”(hŒWUsed with ``event`` and ``notify``, specifies which multicast group message belongs to.”h]”(hŒ Used with ”…””}”(hj hžhhŸNh Nubj)”}”(hŒ ``event``”h]”hŒevent”…””}”(hj(hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj ubhŒ and ”…””}”(hj hžhhŸNh Nubj)”}”(hŒ ``notify``”h]”hŒnotify”…””}”(hj:hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj ubhŒ5, specifies which multicast group message belongs to.”…””}”(hj hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mihjhžhubjk)”}”(hŒ.. _attr_list:”h]”h}”(h]”h ]”h"]”h$]”h&]”jvŒ attr-list”uh1jjh MlhjhžhhŸh³ubeh}”(h]”Œmcgrp”ah ]”h"]”Œmcgrp”ah$]”h&]”uh1h´hj»hžhhŸh³h Mgubeh}”(h]”Œoperation-properties”ah ]”h"]”Œoperation properties”ah$]”h&]”uh1h´hjhžhhŸh³h M:ubhµ)”}”(hhh]”(hº)”}”(hŒMessage attribute list”h]”hŒMessage attribute list”…””}”(hjphžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjmhžhhŸh³h MoubhÊ)”}”(hŒ~``request``, ``reply`` and ``event`` properties have a single ``attributes`` property which holds the list of attribute names.”h]”(j)”}”(hŒ``request``”h]”hŒrequest”…””}”(hj‚hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj~ubhŒ, ”…””}”(hj~hžhhŸNh Nubj)”}”(hŒ ``reply``”h]”hŒreply”…””}”(hj”hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj~ubhŒ and ”…””}”(hj~hžhhŸNh Nubj)”}”(hŒ ``event``”h]”hŒevent”…””}”(hj¦hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj~ubhŒ properties have a single ”…””}”(hj~hžhhŸNh Nubj)”}”(hŒ``attributes``”h]”hŒ attributes”…””}”(hj¸hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhj~ubhŒ2 property which holds the list of attribute names.”…””}”(hj~hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h MqhjmhžhubhÊ)”}”(hŒ¹Messages can also define ``pre`` and ``post`` properties which will be rendered as ``pre_doit`` and ``post_doit`` calls in the kernel (these properties should be ignored by user space).”h]”(hŒMessages can also define ”…””}”(hjÐhžhhŸNh Nubj)”}”(hŒ``pre``”h]”hŒpre”…””}”(hjØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÐubhŒ and ”…””}”(hjÐhžhhŸNh Nubj)”}”(hŒ``post``”h]”hŒpost”…””}”(hjêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÐubhŒ& properties which will be rendered as ”…””}”(hjÐhžhhŸNh Nubj)”}”(hŒ``pre_doit``”h]”hŒpre_doit”…””}”(hjühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÐubhŒ and ”…””}”hjÐsbj)”}”(hŒ ``post_doit``”h]”hŒ post_doit”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjÐubhŒH calls in the kernel (these properties should be ignored by user space).”…””}”(hjÐhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mthjmhžhubeh}”(h]”(Œmessage-attribute-list”j\eh ]”h"]”(Œmessage attribute list”Œ attr_list”eh$]”h&]”uh1h´hjhžhhŸh³h MojÖ }”j,jRsjØ }”j\jRsubhµ)”}”(hhh]”(hº)”}”(hŒmcast-groups”h]”hŒmcast-groups”…””}”(hj4hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj1hžhhŸh³h MyubhÊ)”}”(hŒ6This section lists the multicast groups of the family.”h]”hŒ6This section lists the multicast groups of the family.”…””}”(hjBhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M{hj1hžhubhµ)”}”(hhh]”(hº)”}”(hŒlist”h]”hŒlist”…””}”(hjShžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjPhžhhŸh³h M~ubhÊ)”}”(hŒRThe only property of ``mcast-groups`` for ``genetlink``, holds the list of groups.”h]”(hŒThe only property of ”…””}”(hjahžhhŸNh Nubj)”}”(hŒ``mcast-groups``”h]”hŒmcast-groups”…””}”(hjihžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjaubhŒ for ”…””}”(hjahžhhŸNh Nubj)”}”(hŒ ``genetlink``”h]”hŒ genetlink”…””}”(hj{hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jŒhjaubhŒ, holds the list of groups.”…””}”(hjahžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M€hjPhžhubeh}”(h]”Œid9”ah ]”h"]”h$]”j±ah&]”uh1h´hj1hžhhŸh³h M~jÖKubeh}”(h]”Œmcast-groups”ah ]”h"]”Œmcast-groups”ah$]”h&]”uh1h´hjhžhhŸh³h Myubhµ)”}”(hhh]”(hº)”}”(hŒMulticast group properties”h]”hŒMulticast group properties”…””}”(hj¥hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¢hžhhŸh³h M„ubhµ)”}”(hhh]”(hº)”}”(hŒname”h]”hŒname”…””}”(hj¶hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj³hžhhŸh³h M‡ubhÊ)”}”(hŒ•Uniquely identifies the multicast group in the family. Similarly to Family ID, Multicast Group ID needs to be resolved at runtime, based on the name.”h]”hŒ•Uniquely identifies the multicast group in the family. Similarly to Family ID, Multicast Group ID needs to be resolved at runtime, based on the name.”…””}”(hjÄhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M‰hj³hžhubjk)”}”(hŒ.. _attr_types:”h]”h}”(h]”h ]”h"]”h$]”h&]”jvŒ attr-types”uh1jjh Mhj³hžhhŸh³ubeh}”(h]”Œid10”ah ]”h"]”h$]”Œname”ah&]”uh1h´hj¢hžhhŸh³h M‡jÖKubeh}”(h]”Œmulticast-group-properties”ah ]”h"]”Œmulticast group properties”ah$]”h&]”uh1h´hjhžhhŸh³h M„ubeh}”(h]”Œ genetlink”ah ]”h"]”Œ genetlink”ah$]”h&]”uh1h´hh¶hžhhŸh³h KLubhµ)”}”(hhh]”(hº)”}”(hŒAttribute types”h]”hŒAttribute types”…””}”(hjøhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjõhžhhŸh³h MubhÊ)”}”(hŒ©This section describes the attribute types supported by the ``genetlink`` compatibility level. Refer to documentation of different levels for additional attribute types.”h]”(hŒjàjejajæjšjgj j j_jj\jmj(jmjœj1j•jPjçj¢jßj³jÜjõjjõjuj&j—j{j”jjÐjjújÙj!jjÂj'jûjÈuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œcollections”ŒCounter”“”}”jEK s…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "name".”h]”hŒ+Duplicate implicit target name: â€œnameâ€.”…””}”(hj§hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhj¤ubah}”(h]”h ]”h"]”h$]”h&]”jjaŒlevel”KŒtype”ŒINFO”Œsource”h³Œline”Keuh1j¢hjIhžhhŸh³h Keubj£)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "name".”h]”hŒ+Duplicate implicit target name: â€œnameâ€.”…””}”(hjÃhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjÀubah}”(h]”h ]”h"]”h$]”h&]”jaŒlevel”KŒtype”j½Œsource”h³Œline”K£uh1j¢hjÙhžhhŸh³h K£ubj£)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "name".”h]”hŒ+Duplicate implicit target name: â€œnameâ€.”…””}”(hjÞhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjÛubah}”(h]”h ]”h"]”h$]”h&]”jºaŒlevel”KŒtype”j½Œsource”h³Œline”K¼uh1j¢hj™hžhhŸh³h K¼ubj£)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "type".”h]”hŒ+Duplicate implicit target name: â€œtypeâ€.”…””}”(hjùhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjöubah}”(h]”h ]”h"]”h$]”h&]”j aŒlevel”KŒtype”j½Œsource”h³Œline”KÁuh1j¢hjÀhžhhŸh³h KÁubj£)”}”(hhh]”hÊ)”}”(hŒ(Duplicate implicit target name: "value".”h]”hŒ,Duplicate implicit target name: â€œvalueâ€.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjubah}”(h]”h ]”h"]”h$]”h&]”jÐ aŒlevel”KŒtype”j½Œsource”h³Œline”KÈuh1j¢hj hžhhŸh³h KÈubj£)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "name".”h]”hŒ+Duplicate implicit target name: â€œnameâ€.”…””}”(hj/hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhj,ubah}”(h]”h ]”h"]”h$]”h&]”jíaŒlevel”KŒtype”j½Œsource”h³Œline”M=uh1j¢hjÌhžhhŸh³h M=ubj£)”}”(hhh]”hÊ)”}”(hŒ(Duplicate implicit target name: "value".”h]”hŒ,Duplicate implicit target name: â€œvalueâ€.”…””}”(hjJhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjGubah}”(h]”h ]”h"]”h$]”h&]”j8aŒlevel”KŒtype”j½Œsource”h³Œline”MBuh1j¢hjóhžhhŸh³h MBubj£)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "list".”h]”hŒ+Duplicate implicit target name: â€œlistâ€.”…””}”(hjehžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjbubah}”(h]”h ]”h"]”h$]”h&]”j•aŒlevel”KŒtype”j½Œsource”h³Œline”M~uh1j¢hjPhžhhŸh³h M~ubj£)”}”(hhh]”hÊ)”}”(hŒ'Duplicate implicit target name: "name".”h]”hŒ+Duplicate implicit target name: â€œnameâ€.”…””}”(hj€hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhj}ubah}”(h]”h ]”h"]”h$]”h&]”jßaŒlevel”KŒtype”j½Œsource”h³Œline”M‡uh1j¢hj³hžhhŸh³h M‡ubeŒtransform_messages”]”(j£)”}”(hhh]”hÊ)”}”(hhh]”hŒ:Hyperlink target "attribute-properties" is not referenced.”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjšubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j½Œsource”h³Œline”K¶uh1j¢ubj£)”}”(hhh]”hÊ)”}”(hhh]”hŒ0Hyperlink target "assign-val" is not referenced.”…””}”hj·sbah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhj´ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j½Œsource”h³Œline”KÅuh1j¢ubj£)”}”(hhh]”hÊ)”}”(hhh]”hŒ/Hyperlink target "attr-list" is not referenced.”…””}”hjÑsbah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjÎubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j½Œsource”h³Œline”Mluh1j¢ubj£)”}”(hhh]”hÊ)”}”(hhh]”hŒ0Hyperlink target "attr-types" is not referenced.”…””}”hjësbah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjèubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j½Œsource”h³Œline”Muh1j¢ubj£)”}”(hhh]”hÊ)”}”(hhh]”hŒ.Hyperlink target "pad-type" is not referenced.”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j½Œsource”h³Œline”M±uh1j¢ubeŒtransformer”NŒinclude_log”]”Œ decoration”Nhžhub.