Hello Stephen,
+static __rte_always_inline
+char *parse_hairpin_map_entry(char *input, char **next)
+{
+ char *tail = strchr(input, ':');
+
+ if (!tail)
+ return NULL;
+ tail[0] = '\0';
+ *next = tail + 1;
+ return input;
+}
+
There is no reason to mark this as
On Thu, 28 Sep 2023 16:39:06 +0300
Gregory Etelson wrote:
> +static __rte_always_inline
> +char *parse_hairpin_map_entry(char *input, char **next)
> +{
> + char *tail = strchr(input, ':');
> +
> + if (!tail)
> + return NULL;
> + tail[0] = '\0';
> + *next = tail + 1;
>
Hairpin offloads packet forwarding.
Packet is expected on Rx port , Rx queue and is delivered
to Tx port Tx queue .
Testpmd implements a static hairpin configuration scheme.
The scheme implicitly matches next valid port for given or .
That approach can be used in a single or double port setups
Testpmd hairpin implementation always sets the next valid port to
complete hairpin binding. That limits hairpin configuration options.
The new parameter allows explicit selection of Rx and Tx ports and
queues in hairpin configuration.
The new `hairpin-map` parameter is provided with 5 parameters,
4 matches
Mail list logo
