Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

2018-04-05 Thread Ben Pfaff
On Thu, Apr 05, 2018 at 07:31:35PM +0200, Alan Kayahan wrote: > OVS patch ports allow the propagation of the metadata (e.g. flow context) > across the connected switches. > > Is there an option to disable the metadata propagation feature? I need this > for my research to benchmark certain

[ovs-discuss] About getting processing delay

2018-04-05 Thread MA Moyeen
Hi I'm interested to measure the delays associated with flow table matching. how can I get time of entrance and exit of a packet in OVS? Given that packets are not control message so no packet in will occur to the Ryu Controller. I'm using mininet, openflow 1.3, OVS and Ryu Controller. Thanking

[ovs-discuss] Is there an option to disable metadata propagation on patch ports?

2018-04-05 Thread Alan Kayahan
Hello, OVS patch ports allow the propagation of the metadata (e.g. flow context) across the connected switches. Is there an option to disable the metadata propagation feature? I need this for my research to benchmark certain behavior. Or patch ports become nothing but veth pairs when this

Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

2018-04-05 Thread Alan Kayahan
Thatis my question and theory :) How can I see that? Can you point me to the code where such decision is taken? 2018-04-05 20:39 GMT+02:00 Ben Pfaff : > What metadata is propagating? > > On Thu, Apr 05, 2018 at 08:14:51PM +0200, Alan Kayahan wrote: > > I introduced a new 32bit

Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

2018-04-05 Thread Alan Kayahan
I introduced a new 32bit field in flow.h to match on. A push_header action appends a header, which contains TLVs, to the packet and sets this field for the first time. An increment action sets this field to a value that resides in the first TLV, if increment action is called again, the field is

Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

2018-04-05 Thread Ben Pfaff
What metadata is propagating? On Thu, Apr 05, 2018 at 08:14:51PM +0200, Alan Kayahan wrote: > I introduced a new 32bit field in flow.h to match on. A push_header action > appends a header, which contains TLVs, to the packet and sets this field > for the first time. An increment action sets this

Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

2018-04-05 Thread Ben Pfaff
compose_output_action__(), in ofproto/ofproto-dpif-xlate.c, clears metadata for patch port traversals in the block that begins "if (xport->peer)", with this code: flow->metadata = htonll(0); memset(>tunnel, 0, sizeof flow->tunnel); memset(flow->regs, 0, sizeof flow->regs);