target: Application: l2fwd CMD: `./build/l2fwd --vdev=net_tap0 --vdev=net_memif,role=master -l 8,51 --socket-mem=128,0 --socket-limit=1024,0 --file-prefix=1 --proc-type=primary --no-pci -- -p 0x3 -T 1` Error: `EAL: Error - exiting with code: 1 Cause: rte_eth_promiscuous_enable:err=Operation not supported, port=1` Possible reason: in file `"rte_eth_memif.c"` for ` struct eth_dev_ops ops`, absence of ".promiscuous_enable & .promiscuous_disable"
Jakub, Can you please take a look? Thanks
I recently addressed similar issue, this patch should fix promiscuous mode for memif pmd: https://patchwork.dpdk.org/patch/68666/
@jakub, the patch shared has `data->promiscuous = 1;`. Is there a function to get or set promiscuous? @Ajith: this looks like a confirmed issue for the DPDk version 20.02. Can this be updated as same.
memif works in promiscuous mode only, but ethdev APIs will work. rte_eth_promiscuous_enable returns success, rte_eth_promiscuous_disable returns error as memif only works in promiscuous mode, and rte_eth_promiscuous_get returns 1.
thanks @jakub for the explanation that memif is always promiscuous. I am ok with this approach, we can close this.
Thanks Jakub. Closing this since its working as expected.
Hi Ajit & Jakub, the bug is actually confirmed in 20.02. As I understand the patch will fix the same in 20.05. If this information is correct, I am not sure `INVALID` is right bug state. Should not it be confirmed, and fixed by patch?
Right. I missed that the fix is in 20.05 In that case it cannot be set as invalid. 20.02 is not LTS release and 20.05-rc1 is out. So mark it as wontfix then?
thanks Ajit, with this information we can recommend users and customers for 20.05 for memif.