it really matter whether it is due to an action, or a
configuration option ( hard-coded action if you will )?
Regards,
Jeroen
On Tue, Jun 21, 2016 at 4:29 PM, Jesse Gross <je...@kernel.org> wrote:
> On Mon, Jun 20, 2016 at 8:40 AM, Jeroen van Bemmel <jvb...@gmail.com> wrote:
>&
Hello,
When using VXLAN over Internet connections, Openvswitch TCP
performance is currently limited due to IP fragmentation: The Internet
MTU is (at most) 1500 bytes, and the typical TCP MSS value of 1460
bytes used by clients becomes 1460+40+50 VXLAN = 1550 bytes.
The attached patch addresses
You're very welcome - and who knows, you may find yourself in a
situation where you will need these options. Always good to give users
a choice
We really should add some test cases for this - I managed to run 'make
check' on a regular Ubuntu server just now, must have had something to
do with my
---
NEWS | 5 +++
include/openflow/nicira-ext.h | 23 +-
lib/bundle.c | 4 +++
lib/flow.c| 73 ++-
lib/flow.h| 2 ++
lib/multipath.c | 4 +++
Changes:
* Adhere to coding standards ( removed spaces before/after (), no // comments )
* Fix NEWS item
* Use 'bool' instead of 'int'
Signed-Off-By: Jeroen van Bemmel jvb...@gmail.com
Suggested-by: Ben Pfaff b...@nicira.com
___
dev mailing list
dev
The symmetric_l4 function implements a hash over various fields
including L2 fields such as ethernet source and destination MAC.
Inspite of its name, there are situations in which this hash does not
yield symmetric results ( e.g. when using VRRP, where the router
receives packets on a virtual MAC
The symmetric_l4 function implements a hash over various fields
including L2 fields such as ethernet source and destination MAC.
Inspite of its name, there are situations in which this hash does not
yield symmetric results ( e.g. when using VRRP, where the router
receives packets on a virtual MAC
