This is a bit trickier, but it's certainly possible. First, you'll need to
configure queues on the egress ports. You can see how to do this in the
"Quality of Service (QoS)" section of the ovs-vsctl man page:
http://openvswitch.org/cgi-bin/ovsman.cgi?page=utilities%2Fovs-vsctl.8
Then, you can add flows with the "enqueue" action from your controller or the
ovs-ofctl command. The enqueue action takes the port number and the queue id
you configured earlier. You can see some documentation about the enqueue
action in the OpenFlow spec or the ovs-ofctl man page:
http://openvswitch.org/cgi-bin/ovsman.cgi?page=utilities%2Fovs-ofctl.8
Good luck!
--Justin
On Aug 29, 2011, at 8:58 PM, Trinh Minh Tri wrote:
> Dear openvswitch dev!
>
> I'm newbie in openvswitch but feel very interested in it to set up my
> experimental evvironment. In my experiment, I need to use the flow rate
> limiting feature to limit the rate of each flow comming in to openvswitch. I
> have searched in the openvswitch website and found out this document of QoS
> rate limiting http://openvswitch.org/?page_id=267. But this document only
> limit the rate for all traffic entering the openvswitch port. I would like to
> ask whether is there any solution in openvswitch to classify the traffic as
> flow and apply the QoS rate limiting to each flow.
>
> Thank you very much
> Trinh Minh Tri
>
>
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
