Lines Matching full:flow

4 ibv_create_flow, ibv_destroy_flow \- create or destroy flow steering rules
18 to be attached into a specified flow
19 .I flow
63 IBV_FLOW_SPEC_ETH                       = 0x20,   /* Flow specification of L2 header */
64 IBV_FLOW_SPEC_IPV4                      = 0x30,   /* Flow specification of IPv4 header */
65 IBV_FLOW_SPEC_IPV6                      = 0x31,   /* Flow specification of IPv6 header */
66 IBV_FLOW_SPEC_IPV4_EXT                  = 0x32,   /* Extended flow specification of IPv4 */
67 IBV_FLOW_SPEC_TCP                       = 0x40,   /* Flow specification of TCP header */
68 IBV_FLOW_SPEC_UDP                       = 0x41,   /* Flow specification of UDP header */
69 IBV_FLOW_SPEC_VXLAN_TUNNEL             	= 0x50,   /* Flow specification of VXLAN header */
77 Flow specification general structure:
82 uint16_t  size;                  /* Flow specification size = sizeof(struct ibv_flow_spec_xxx) */
96 .SS Flow domains and priority
97 Flow steering defines the concept of domain and priority. Each domain represents an application tha…
98 … priority domain will always supersede a lower priority domain when their flow specifications over…
104 …t to note that the priority value of a flow spec is used not only to establish the precedence of c…
105 but also as a way to abstract the order on which flow specs are tested for matches. Flows with high…
108 destroys the flow
112 returns a pointer to the flow, or NULL if the request fails. In case of an error, errno is updated.
119 flow specification, QP or priority are invalid
124 Couldn't create/destroy flow, not enough memory
126 Device managed flow steering isn't currently supported
128 No permissions to add the flow steering rule