Re: [dpdk-dev] [PATCH] net/af_packet: add docs guide

2018-12-18 Thread Lam, Tiago
On 18/12/2018 00:39, Ferruh Yigit wrote: > On 12/18/2018 12:31 AM, Ferruh Yigit wrote: >> On 12/17/2018 9:14 AM, Tiago Lam wrote: >>> As of commit 364e08f2bbc0, DPDK allows an aplication to send and receive >>> raw packets using an AF_PACKET and PACKET_MMAP, when using a Linux >>> Kernel. This comp

Re: [dpdk-dev] [PATCH v2 3/3] net/af_packet: get 'framesz' from the iface's MTU

2018-12-17 Thread Lam, Tiago
Hi Ferruh, On 28/11/2018 13:33, Ferruh Yigit wrote: > On 11/28/2018 1:12 PM, Lam, Tiago wrote: >> On 27/11/2018 17:43, Ferruh Yigit wrote: >>> On 11/20/2018 10:26 AM, Tiago Lam wrote: >>>> Use the underlying MTU to calculate the framsize to be used for the mmap >&

Re: [dpdk-dev] [PATCH v2 3/3] net/af_packet: get 'framesz' from the iface's MTU

2018-11-28 Thread Lam, Tiago
On 27/11/2018 17:43, Ferruh Yigit wrote: > On 11/20/2018 10:26 AM, Tiago Lam wrote: >> Use the underlying MTU to calculate the framsize to be used for the mmap >> RINGs. This is to make it more flexible on deployments with different >> MTU requirements, instead of using a pre-defined value of 2048B

Re: [dpdk-dev] [PATCH v2 1/3] net/af_packet: set_mtu() decrements sockaddr twice

2018-11-20 Thread Lam, Tiago
On 20/11/2018 10:29, Kevin Traynor wrote: > On 11/20/2018 10:26 AM, Tiago Lam wrote: >> When setting the MTU, eth_dev_mtu_set() is called to validate the >> provided MTU. As part of that, it calculates the useful area to store >> data and compares it against the MTU, to guarantee that there's en

Re: [dpdk-dev] af_packet dev default "framesz" of 2048B

2018-11-20 Thread Lam, Tiago
On 16/11/2018 17:20, Ferruh Yigit wrote: > On 11/15/2018 7:02 PM, Lam, Tiago wrote: >> Hi guys, >> >> OvS-DPDK has recently had small a change that changed the data room >> available in an mbuf (commit dfaf00e in OvS). This seems to have had the >> consequence

[dpdk-dev] af_packet dev default "framesz" of 2048B

2018-11-15 Thread Lam, Tiago
Hi guys, OvS-DPDK has recently had small a change that changed the data room available in an mbuf (commit dfaf00e in OvS). This seems to have had the consequence of breaking the initialisation of eth_af_packets interfaces, when using default values ("options:dpdk- devargs=eth_af_packet0,iface=enp6