Add support for limiting the CT zone usage per Ls, LR or LSP.
When the limit is configured on logical switch it will also implicitly
set limits for all ports in that logical switch. The port configuration
can be overwritten individually and has priority over the whole logical
switch configuration.
In order to be able to store CT limits for specified zone, store the
zone inside separate struct instead of simap. This allows to add
the addition of limit without changing the whole infrastructure again.
This is a preparation step for the CT zone limits.
Signed-off-by: Ales Musil
---
v3: Rebase
Move the CT zone handling specific bits into its own module. This
allows for easier changes done within the module and separates the
logic that is unrelated from ovn-controller.
Signed-off-by: Ales Musil
---
v3: Rebase on top of latest main.
---
controller/automake.mk | 4 +-
controller/c
Move more code into the new ct-zone module and encapsulate
functionality that is strictly related to CT zone handling.
Signed-off-by: Ales Musil
---
v3: Rebase on top of latest main.
---
controller/ct-zone.c| 156 +---
controller/ct-zone.h| 8 +-
Add ability that allows to set CT limits per logical switch, logical
router or logical switch port. When the limit is applied to logical
switch it will be implicitly set for all logical ports in the logical
switch. This can be overwritten individually per port.
To achieve this there is a small ref
On Fri, Jun 14, 2024 at 05:11:30PM GMT, Simon Horman wrote:
> On Mon, Jun 03, 2024 at 08:56:38PM +0200, Adrian Moreno wrote:
> > Although not explicitly documented in the psample module itself, the
> > definition of PSAMPLE_ATTR_SAMPLE_RATE seems inherited from act_sample.
> >
> > Quoting tc-sample
From: Wilson Peng
v2-v3 change: Remove the unneeded sanity check and just correct the failure
when OvsNatInit is called failed.
While deploying Tanzu Kubernetes(Antrea based solution) in Broadcom customer,
Sometimes it is found that the kernel thread OvsConntrackEntryCleaner is not
Started after
From: Wilson Peng
v2-v3 change: Remove the unneeded sanity check and just correct the failure
when OvsNatInit is called failed.
While deploying Tanzu Kubernetes(Antrea based solution) in Broadcom customer,
Sometimes it is found that the kernel thread OvsConntrackEntryCleaner is not
Started after
I found another cause of this BUG:
```
In public-ovs code, @netdev_offload_dpdk and @netdev_offload_tc is register
in @netdev_register_flow_api_provider.
The @netdev_register_flow_api_provider is called in init stage,
like @dpdk_init__ and @netdev_initialize.
After register, @netdev_offload_dpdk an
Oh, I'm using ovs-2.17.2, and I found that there is no .meter_set api
implement in ovs-dpdk, which means only one .meter_set implement in TC.
```
const struct netdev_flow_api netdev_offload_dpdk = {
.type = "dpdk_flow_api",
.flow_put = netdev_offload_dpdk_flow_put,
.flow_del = netdev_of
On Thu, Jun 13, 2024 at 02:13:33PM -0400, Aaron Conole wrote:
> The pmtu testing will require that the OVS module is installed,
> so do that.
>
> Signed-off-by: Aaron Conole
Reviewed-by: Simon Horman
Tested-by: Simon Horman
___
dev mailing list
d...
On Thu, Jun 13, 2024 at 02:13:29PM -0400, Aaron Conole wrote:
> These will be used in upcoming commits to set specific attributes for
> interacting with tunnels. Since set() will use the key parsing routine, we
> also make sure to prepend it with an open paren, for the action parsing to
> properly
On Thu, Jun 13, 2024 at 02:13:28PM -0400, Aaron Conole wrote:
> Until recently, the ovs-dpctl utility was used with a limited actions set
> and didn't need to have support for multiple similar actions. However,
> when adding support for tunnels, it will be important to support multiple
> set() act
On Thu, Jun 13, 2024 at 02:13:31PM -0400, Aaron Conole wrote:
> The current iteration of IPv6 support requires explicit fields to be set
> in addition to not properly support the actual IPv6 addresses properly.
> With this change, make it so that the ipv6() bare option is usable to
> create wildcar
On Thu, Jun 13, 2024 at 02:13:30PM -0400, Aaron Conole wrote:
> This will be used when setting details about the tunnel to use as
> transport. There is a difference between the ODP format between tunnel():
> the 'key' flag is not actually a flag field, so we don't support it in the
> same way that
On Thu, Jun 13, 2024 at 02:13:27PM -0400, Aaron Conole wrote:
> The OVS module can operate in conjunction with various types of
> tunnel ports. These are created as either explicit tunnel vport
> types, OR by creating a tunnel interface which acts as an anchor
> for the lightweight tunnel support.
16 matches
Mail list logo
