On 09/22/14 at 07:16pm, Tom Herbert wrote: > Turn on UDP RSS on the device and I bet you'll see those differences > go away! Once we moved to UDP encapsulation, there's really little > value in looking at inner headers for RSS or ECMP, this should be > sufficient. Sure someone might want to parse the inner headers for > some sort of advanced RX steering, but again this implies rx-filtering > and not switch functionality.
Agreed. The reason we discuss this in the context of this thread is because the required rx-filtering capabilities seem to be introduced in the form of (adapted) switch chip integrations onto NICs. In that sense, OVS is essentially doing advanced RX steering in software. I agree that switch functionality (whatever that specifically implies) is not strictly required for the host if you consider queue redirection as part of RX steering. The exception here would be use of SR-IOV which could be highly interesting for corner cases if combined with smart elephant guest detection. A classic example would be NFV deployed in a virtualized environment, i.e. a virtual firewall or DPI application serving a bunch of guests. > If this is something that doesn't require any model change to the > stack and is just a clever backend for rx-filters or tc, then I'm fine > with that! I haven't seen any model change proposed. I'm most certainly not advocating that. Anyone who can live a model change might as well just stick to SnabbSwitch or DPDK. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
