We try to implement the minimum interface that we can in the kernel. Usually
the TTL doesn't change across a flow, so matching on a particular TTL value and
setting a new value isn't a problem. Plus, it allows us flexibility to stack
multiple OpenFlow decrements (useful for logical routers,
Hello,
I see that there is an action OFPACT_DEC_TTL in user space, but not in
kernel space for OVS. Is there a reason why kernel space action is not
implemented? If one has to implement the kernel space action
OFPACT_DEC_TTL, what will be the approach? The reason I want to have kernel
space
On 6/24/2019 1:03 PM, Murali Veluru wrote:
Hi All,
I am testing ovs-dpdk performance test with the help of IPERF.
I created VM using qemu command.
I assigned IP 10.0.1.16 to VM and other device IP is 10.0.1.18 (Dev2). I
am able to ping and able to run IPERF.
It is giving average output
Hi All,
I am testing ovs-dpdk performance test with the help of IPERF.
I created VM using qemu command.
I assigned IP 10.0.1.16 to VM and other device IP is 10.0.1.18 (Dev2). I am
able to ping and able to run IPERF.
It is giving average output ~3.5G form VM to DEV2 on 10G physical interface.
I am running Ubuntu on virtualized hosts, along with VXLAN. However, the VXLAN
performance has been poor. I am trying to verify the VM environment. Any
recommendations from a performance tuning perspective? Is it possible to get
good performance with VXLAN in virtual hardware, or would I be
On Mon, Jun 24, 2019 at 1:51 PM aginwala wrote:
> Hi:
> As per irc meeting discussion, some nice findings were already discussed
> by Numan (Thanks for sharing the details). When changing external_ids for
> a claimed port e.g. ovn-nbctl set logical_switch_port sw0-port1
> external_ids:foo=bar
Hi:
As per irc meeting discussion, some nice findings were already discussed by
Numan (Thanks for sharing the details). When changing external_ids for a
claimed port e.g. ovn-nbctl set logical_switch_port sw0-port1
external_ids:foo=bar triggers re-computation on local compute. I do see the
same
