Differences

This shows you the differences between two versions of the page.

--- mywiki:linux:generic_netlink [2015/05/16 08:50] – [Define attribute policy] shaoguoh
+++ mywiki:linux:generic_netlink [2019/09/15 18:55] (current) – external edit 127.0.0.1
@@ Line 95: / Line 95: @@
 </file>
+{{:mywiki:linux:message_hdr.png|}}
+{{:mywiki:linux:message_map.png|}}
 ====== Procedure in kernel ======
@@ Line 223: / Line 226: @@
 </file>
+===== Define attribute =====
+<file>
+</file>
+Notes: Attributes And Message Payloads
+Most common data structures can be represented with Netlink attributes:
+    scalar values: Most scalar values already have well-defined attribute types;
+    Arrays: Arrays can be represented by using a single nested attribute as a container with several of the same attribute type inside each representing a spot in the array.
+It is also important to use unique attributes as much as possible. This helps make the most of the Netlink attribute mechanisms and provides for easy changes to the message format in the future.
 ===== Define Message structure =====
@@ Line 257: / Line 279: @@
 </file>
-===== Define attribute =====
-<file>
-</file>
-Notes: Attributes And Message Payloads
-Most common data structures can be represented with Netlink attributes:
-    scalar values: Most scalar values already have well-defined attribute types;
-    Arrays: Arrays can be represented by using a single nested attribute as a container with several of the same attribute type inside each representing a spot in the array.
-It is also important to use unique attributes as much as possible. This helps make the most of the Netlink attribute mechanisms and provides for easy changes to the message format in the future.