On Wed, Dec 16, 2020 at 08:31:44AM -0800, Alexander Duyck wrote: > You say this will scale better but I am not even sure about that. The > fact is SR-IOV could scale to 256 VFs, but for networking I kind of > doubt the limitation would have been the bus number and would more > likely be issues with packet replication and PCIe throughput, > especially when you start dealing with east-west traffic within the > same system. We have been seeing deployments already hitting the 256 limit. This is not a "theoretical use" patch set. There are already VM and container farms with SW networking that support much more than 256 VM/containers per server. The optimization here is to reduce the hypervisor workload and free up CPU cycles for the VMs/containers to consume. This means less handling of packets in the CPU, especially for VM cases w/ SRIOV or VDPA. Even the extra DMA on the NIC is not really a big deal. These are 400G NICs with big fast PCI. If you top them out you are already doing an aggregate of 400G of network traffic. That is a big number for a single sever, it is OK. Someone might feel differently if they did this on a 10/40G NIC, in which case this is not the solution for their application. > Sorry you used the word "replace", and my assumption here was that the > goal is to get something in place that can take the place of SR-IOV so > that you wouldn't be maintaining the two systems at the same time. > That is my concern as I don't want us having SR-IOV, and then several > flavors of SIOV. We need to decide on one thing that will be the way > forward. SRIOV has to continue until the PASID and IMS platform features are widely available and mature. It will probably be 10 years before we see most people able to use SIOV for everything they want. I think we will see lots of SIOV varients, I know Intel is already pushing SIOV parts outside netdev. > I get that. That is why I said switchdev isn't a standard for the > endpoint. One of the biggest issues with SR-IOV that I have seen is > the fact that the last piece isn't really defined. We never did a good > job of defining how the ADI should look to the guest and as a result > it kind of stalled in adoption. The ADI is supposed to present the HW programming API that is desired. It is always up to the implementation. SIOV was never a project to standardize HW programming models like virtio-net, NVMe, etc. > > I'm a bit surprised HW that can do macvlan can't be modeled with > > switchdev? What is missing? > > If I recall it was the fact that the hardware defaults to transmitting > everything that doesn't match an existing rule to the external port > unless it comes from the external port. That seems small enough it should be resolvable, IMHO. eg some new switch rule that matches that specific HW behavior? > Something like the vdpa model is more like what I had in mind. Only > vdpa only works for the userspace networking case. That's because making a driver that converts the native HW to VDPA and then running a generic netdev on the resulting virtio-net is a pretty wild thing to do. I can't really think of an actual use case. > Basically the idea is to have an assignable device interface that > isn't directly tied to the hardware. The switchdev model is to create a switch port. As I explained in Linux we see "pci device" and "aux device" as being some "user port" options to access to that switch. If you want a "generic device" that is fine, but what exactly is that programming interface in Linux? Sketch out an API, where does the idea go? What does the driver that implement it look like? What consumes it? Should this be a great idea, then a mlx5 version of this will still be to create an SF aux device, bind mlx5_core, then bind "generic device" on top of that. This is simply a reflection of how the mlx5 HW/SW layering works. Squashing all of this into a single layer is work with no bad ROI. > they are pushed into containers you don't have to rip them out if for > some reason you need to change the network configuration. Why would you need to rip them out? Jason
