On 29/02/2016 11:07, "Ben Pfaff" <b...@ovn.org> wrote: >On Sun, Feb 28, 2016 at 12:13:12PM -0800, Daniele Di Proietto wrote: >> Currently we treat set_multiq() calls specially in netdev and >>dpif-netdev: >> every pmd thread must be stopped and set_multiq() is allowed to destroy >>and >> recreate the device. >> >> I think we can improve this by: >> * Generalizing the mechanism to allow changing other parameters at >>runtime >> (such as MTU). >> * Involving less the above layer (dpif-netdev). The request for changes >> often comes from below (netdev_dpdk_set_config(), or the vhost >>new_device() >> callback). There's no need for dpif-netdev to remember the requested >>value, >> all that it needs to know is that a configuration change is requested. >> >> This series implements exactly this: a mechanism to allow a netdev >>provider >> to request configuration changes, to which dpif-netdev will respond by >> stopping rx/tx and calling a netdev function to appy the new >>configuration. > >Let me know if you want me to review any of these.
I think I can use your input on this series, so I'd appreciate a review, thanks! _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
