Thanks for your attention. My work is on network of IaaS, and I want use it for network nodes, use openflow set_queue as a filter to limit egress SNATed floating IP traffic rate on dpdk port for vpc user.
I also want to expand ingress policing to limit ingress DNATed traffic for vpc user, but I don't kown how to handle filter. Finally, I need to reassemble packets before conntrack on ovs-dpdk, and fragment packets before tunnel port and dpdk port. Thanks zhaozhanxu At 2017-07-20 17:51:57, "Stokes, Ian" <ian.sto...@intel.com> wrote: >> Original command is as below: >> >> $ ovs-vsctl set port vhost-user0 qos=@newqos -- \ >> --id=@newqos create qos type=egress-policer other- >> config:cir=46000000 \ >> other-config:cbs=2048` >> >> Now it can support command as below: >> >> $ ovs-vsctl set port vhost-user0 qos=@newqos -- \ >> --id=@newqos create qos type=egress-policer \ >> other-config:cir=46000000 other-config:cbs=2048` \ >> queues:123=@q123 queues:234=@q234 -- \ >> --id=@q123 create queue other-config:cir=12800000 other- >> config:cbs=2048 -- \ >> --id=@q234 create queue other-config:cir=25600000 other- >> config:cbs=2048` >> >> Then, we can use OpenFlow to direct packet to queues: >> >> $ ovs-ofctl add-flow br0 in_port=5,actions=set_queue:123,normal >> $ ovs-ofctl add-flow br0 in_port=6,actions=set_queue:234,normal >> >> Finally, we can use command `ovs-appctl -t ovs-vswitchd qos/show vhost- >> user0` to show QoS queue information. >> >> Signed-off-by: zhaozhanxu <zhaozha...@163.com> >> >> zhaozhanxu (4): >> Support multi-queue for ovs-dpdk QoS. >> Support multi-queue rate limit function for ovs-dpdk Qos. >> Support to show multi-queue qos info >> Modify QoS configure documents for ovs-dpdk >> >> Documentation/howto/dpdk.rst | 12 +- >> lib/netdev-dpdk.c | 374 >> +++++++++++++++++++++++++++++++++++++++++-- >> 2 files changed, 374 insertions(+), 12 deletions(-) > >Thanks for working on this zhaozhanxu, great to see the QoS for ovs dpdk being >expanded, this was something I intended to revisit at some stage but never got >around to. Will plan to look at the patchset at some stage. > >Out of interest, what's your use case for this? Normally it's ingress policing >that proves more useful for users. (The egress policer was originally added as >a simple example QoS implementation to supplement the QoS API we introduced). > >Thanks >Ian > >> >> -- >> 2.7.4 >> >> >> _______________________________________________ >> dev mailing list >> d...@openvswitch.org >> https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
