On Wed, Sep 16, 2020 at 10:07 AM Alexander Constantinescu <
acons...@redhat.com> wrote:
> In this example it is equivalent to just "ip4.src == 10.244.2.5/32"'.
>>
>
> Yes, I was just using it as an example (though, granted, noop example)
>
> Some background to help steer the discussion:
>
>
>
> In this example it is equivalent to just "ip4.src == 10.244.2.5/32"'.
>
Yes, I was just using it as an example (though, granted, noop example)
Some background to help steer the discussion:
Essentially the functionality here is to have south -> north traffic from
certain logical switch ports
On Wed, Sep 16, 2020 at 5:42 AM Alexander Constantinescu <
acons...@redhat.com> wrote:
>
> Hi
>
> I was wondering if anybody is aware of an IP address signifying "external
IP destinations"?
>
> Currently in OVN we can use the IP address 0.0.0.0/0 for match
expressions in logical routing policies /
Hi
I was wondering if anybody is aware of an IP address signifying "external
IP destinations"?
Currently in OVN we can use the IP address 0.0.0.0/0 for match expressions
in logical routing policies / ACLs when we want to specify a source or
destination IP equating to the pseudo term: "all IP
Hi OVS Team
We are trying to evaluate OVS-DPDK performance on an x86 system and
referring the below document to replicate the same setup
https://download.01.org/packet-processing/ONPS2.1/Intel_ONP_Release_2.1_Performance_Test_Report_Rev1.0.pdf
Table 7-8 discusses having added 1K OVS flows per
Hi ALL,
This problem is fixed, update info as follows:
1) The following patch can fix the problem happened when using the
testing code of the previous mail.
https://www.mail-archive.com/ovs-dev@openvswitch.org/msg41202.html
2) What we need here is a memory_order_acquire
