Thu, Aug 29, 2019 at 03:26:11PM CEST, and...@lunn.ch wrote: >> NACK >> >> This is invalid usecase for switchdev infra. Switchdev is there for >> bridge offload purposes only. > >Hi Jiri > >I would argue this is for bridge offload. In another email, you say >promisc is promisc. Does that mean the Mellonox hardware forwards >every frame ingressing a port to the CPU by default as soon as it is >enslaved to a bridge and promisc mode turned on? Or course not. At the >moment, every switchdev driver wrongly implement promisc mode. > >This patchset is about correctly implementing promisc mode, so that >applications can use it as expected. And that means configuring the >hardware bridge to also forward a copy of frames to the CPU.
Wait, I believe there has been some misundestanding. Promisc mode is NOT about getting packets to the cpu. It's about setting hw filters in a way that no rx packet is dropped. For normal nics it means that all packets get to the cpu, but that is just because it is the only direction they can make. If you want to get packets from the hw forwarding dataplane to cpu, you should not use promisc mode for that. That would be incorrect. If you want to get packets from the hw forwarding dataplane to cpu, you should use tc trap action. It is there exactly for this purpose. Promisc is for setting rx filters. > >I see trap as a different use case. tcpdump/pcap is not going to use >traps. > > Andrew
