Re: [dpdk-users] AVX-512

On Fri, 23 Feb 2018 11:16:14 -0800 Tharaneedharan Vilwanathan wrote: > Hi All, > > I have a quick question. I got a new server with the CPU that should have > AVX-512 support but I don't see it in Linux (Ubuntu 18.04). > > Here is the output: > >

[dpdk-users] AVX-512

Hi All, I have a quick question. I got a new server with the CPU that should have AVX-512 support but I don't see it in Linux (Ubuntu 18.04). Here is the output: auto@auto-virtual-machine:~$ *cat /proc/cpuinfo* processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 85 model name :

Re: [dpdk-users] Suggestions on how to customize the metadata fields of each packet

Thanks a lot for your suggestions, Taking them into account and having a look a this example on userdata field usage (http://dpdk.org/doc/api/examples_2bbdev_app_2main_8c-example.html#a19), I have though the following plan. I think that the most elegant way to do it is to use "userdata" for

[dpdk-users] Suggestions on how to customize the metadata fields of each packet

Hi all, Victor, I suggest taking a closer look at section 7.1. here: http://dpdk.org/doc/guides/prog_guide/mbuf_lib.html The approach chosen by DPDK is to store everything, metadata and packet data, in contiguous memory. That way, network packets will always have 1 to 1 relationship with DPDK

Re: [dpdk-users] [dpdk-dev] Suggestions on how to customize the metadata fields of each packet

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

Re: [dpdk-users] Suggestions on how to customize the metadata fields of each packet

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