Open vSwitch version: 2.5.0, 2.5.2, 2.7.0
Kernel Version: Linux version 3.10.70
OS: Openwrt Barrier Breaker
________________________________________________________________
|
DUT
|
______ | _______________
____________________________ |
___________
| | | | |
| Ovs bridge_1
| | |
|
| | | | |
veth |
| | |
|
| PC1 |-----------------| | lxc-container |
------------------------------| Port [lan_0] Port [ eth1]
| |----------------------------------------------| PC2 |
|_____ | | | |
|____________________________| |
|___________|
| |_______________|
|
|________________________________________________________________|
Scenario:
On PC1 we start to send burst traffic:
300 packets at 185 Mbps; wait 2 seconds;
300 packets at 105 Mbps; wait 2 seconds
300 packets at 65 Mbps; wait 2 seconds
300 packets at 125 Mbps
We are experiencing packet reordering on PC2. After some testing we were able
to pinpoint the problem in Ovs bridge_1.
A flow is added and we can see it with:
ovs-appctl dpif/dump-flows bridge_1
It seems that the packets that are reordered are those that go to userspace
before the flow is added. When the flow becomes active in kernel space the next
packets are forwarded directly without going to userspace.
Can you please tell us if this is a bug or an expected behavior?
Also I want to say that all we want to achieve is a simple Layer-2 bridge so if
you have any idea on how to avoid packet reordering with a simple Layer-2
bridge OvS please let us know.
Thank you in advance for your help,
Ionut.
________________________________
Secure your future - Meet Newtec
Dialog®<http://www.newtec.eu/product/newtec-dialog>, the platform that embraces
change - with award-winning Mx-DMA®<http://www.newtec.eu/technology/mx-dma>!
***mail confidentiality footer ***
This message and any attachments thereto are confidential. They may also be
privileged or otherwise protected by work product immunity or other legal
rules. If you have received it by mistake, please let us know by e-mail reply
and delete it from your system; you may not copy this message or disclose its
contents to anyone. E-mail transmission cannot be guaranteed to be secure or
error free as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore is in no
way liable for any errors or omissions in the content of this message, which
may arise as a result of e-mail transmission. If verification is required,
please request a hard copy.
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
