I think this dpdkbond option is worthy of being supported. In my view, ovs bonding works based on openflow upcall processing. When some slave gets link down, the datapath flows related it will be flushed an revalidated. As a result, that may cause a great deal of upcall requests to be handled and bring packets dropping.
But if we using dpdkbond as an ovs interface , that question is not exist any more. -----邮件原件----- 发件人: [email protected] [mailto:[email protected]] 代表 Ben Pfaff 发送时间: 2018年4月17日 0:55 收件人: Tonghao Zhang <[email protected]> 抄送: Ilya Maximets <[email protected]>; ovs dev <[email protected]> 主题: Re: [ovs-dev] [PATCH net-next 0/6] Add dpdk-bond support On Mon, Apr 16, 2018 at 07:05:04PM +0800, Tonghao Zhang wrote: > On Sat, Apr 14, 2018 at 2:16 AM, Ben Pfaff <[email protected]> wrote: > > On Thu, Apr 12, 2018 at 05:52:46AM -0700, [email protected] wrote: > >> From: Tonghao Zhang <[email protected]> > >> > >> The bond of openvswitch has not good performance. > > > > I'd really say that the best solution to that is to improve the > > performance, rather than piling on another bonding layer. > Yes, i agree that. I think we can also, support an option for users to > use the native dpdk-bond device. > Because I have used the dpdk-bond in our production environment. I use > it as a interface but not a port. > > These patches are RFC and just an option for users, not to replace > ovs-bond function. > If you agree that, I can do works for this. If not, I will drop these patches. My real worry here is that, if we add the feature, we will have to keep it forever even if core OVS bonding's performance catches up with it. I think that it's worth thinking about strategies for making core OVS bonding faster. Do we have good ideas? If we do, then I'd prefer to push in that direction. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
