the use of meta-data in the
> examples/ip_pipeline sample app (see struct app_pkt_metadata in "main.h").
>
> Please let me know if this makes sense?
>
> Regards,
> Cristian
>
> PS: This is where a white board would help a lot ...
>
>
> -Original Me
see struct app_pkt_metadata in "main.h").
>
> Please let me know if this makes sense?
>
> Regards,
> Cristian
>
> PS: This is where a white board would help a lot ...
>
>
> -Original Message-
> From: Ivan Boule [mailto:ivan.boule at 6wind.com]
,
Cristian
PS: This is where a white board would help a lot ...
-Original Message-
From: Ivan Boule [mailto:ivan.bo...@6wind.com]
Sent: Wednesday, May 28, 2014 1:03 PM
To: Dumitrescu, Cristian; dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH 04/29] mbuf: added offset of packet meta-d
n
PS: This is where a white board would help a lot ...
-Original Message-
From: Ivan Boule [mailto:ivan.bo...@6wind.com]
Sent: Wednesday, May 28, 2014 1:03 PM
To: Dumitrescu, Cristian; dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH 04/29] mbuf: added offset of packet meta-data in
the pac
Hi Cristian,
Currently, the DPDK framework does not make any assumption on the actual
layout of a mbuf.
More precisely, the DPDK does not impose any constraint on the actual
location of additional metadata, if any, or on the actual location and
size of its associated payload data buffer.
This is
Added zero-size field (offset in data structure) to specify the beginning of
packet meta-data in the packet buffer just after the mbuf.
The size of the packet meta-data is application specific and the packet
meta-data is managed by the application.
The packet meta-data should always be
6 matches
Mail list logo
