--Original Message-
> > From: konstantin.anan...@intel.com [mailto:konstantin.anan...@intel.com]
> > Sent: Friday, February 23, 2018 4:27 PM
> > To: Victor Huertas ; long...@viettel.com.vn
> > Cc: dev@dpdk.org; us...@dpdk.org
> > Subject: RE: [dpdk-dev] Suggestions on
konstantin.anan...@intel.com [mailto:konstantin.anan...@intel.com]
> Sent: Friday, February 23, 2018 4:27 PM
> To: Victor Huertas ; long...@viettel.com.vn
> Cc: dev@dpdk.org; us...@dpdk.org
> Subject: RE: [dpdk-dev] Suggestions on how to customize the metadata fields
> of each packet
&g
Hi Victor,
>
> Thanks for your quick answer,
>
> I have read so many documents and web pages on this issue that probably I
> confounded the utility of the headroom. It is good to know that this 128
> bytes space is available to my disposal. The fact of being lost once the
> NIC transmits the fra
Thanks for your quick answer,
I have read so many documents and web pages on this issue that probably I
confounded the utility of the headroom. It is good to know that this 128
bytes space is available to my disposal. The fact of being lost once the
NIC transmits the frame it is not a problem at a
Hi,
First, I think your question should be sent to the user mailing list, not
the dev mailing list.
> I have seen that each packet has a headroom memory space (128 bytes long)
> where RSS hashing and other metadata provided by the NIC is stored.
If I'm not mistaken, the headroom is not where met
Hi all,
In the project I am working I need to define custom metadata fields on each
packet once they are captured using DPDK.
I have seen that each packet has a headroom memory space (128 bytes long)
where RSS hashing and other metadata provided by the NIC is stored. This
information will be usefu
6 matches
Mail list logo
