Thank you for the report. After investigation I think I know what is
triggering the loop. It is part of the patch 4/4 rest of it is fine. Once I
have a fix for that I will submit a new version.

On Tue, Jan 28, 2025 at 5:39 PM Enrique Llorente Pastora <
ellor...@redhat.com> wrote:

> After testing with a ovn-kubernetes poc using transit routers with a
> primary UDN
> layer2 topology and migrating a VM with ingress iperf3 traffic I get
> almost 100% of some cpu cores bussy
> with softirq, even after closing the iperf3 client, so feels like a
> loop is there.
>
>   17 root      20   0       0      0      0 R  99.0   0.0  32:04.56
> ksoftirqd/0
>   45 root      20   0       0      0      0 R  90.4   0.0  47:50.90
> ksoftirqd/4
>
> the poc ->
> https://github.com/qinqon/ovn-kubernetes/tree/dnm-transit-router-poc
> (last two commits)
>
> The db files are attached to the email:
>
> On Tue, Jan 21, 2025 at 8:39 AM Ales Musil <amu...@redhat.com> wrote:
> >
> > In order to have transit router we have to allow peer port connection
> > between LR patch port l3gateway types. This allows direct connection
> > of two LRs, one of the being transit router and the second one being
> > GW router. This is taken care of commit 3/6. To be fair this can
> > change can be useful in general even without transit router.
> >
> > The 2/4 and 4/4 is the actual work needed for transit router. First
> > is the way to define remote ports for logical router which on it's
> > own is the main component that results in the transit router. The
> > LRP can be set remote by setting options:requested-chassis to chassis
> > that has is-remote=true. Only one chassis is supported at time. The
> > 6/6 is needed in cases when one AZ ARPs port in other AZ, without
> > this the ARP wouldn't be delivered to the original AZ, which would
> > result in dropped traffic.
> >
> > Ales Musil (4):
> >   physical: Allow l3gateway and patch port to be peers.
> >   northd: Introduce the concept of transit routers.
> >   actions, physical: Make the MC split action generic.
> >   northd, controller: Flood ARP and NA packet on transit router.
> >
> >  NEWS                      |   3 +
> >  controller/lflow.c        |   1 +
> >  controller/lflow.h        |   4 +
> >  controller/physical.c     | 273 ++++++++++++++++++++++++++++++++------
> >  controller/pinctrl.c      |  21 +--
> >  include/ovn/actions.h     |   7 +-
> >  lib/actions.c             |  19 ++-
> >  lib/ovn-util.c            |   2 +-
> >  northd/northd.c           |  52 ++++++--
> >  northd/northd.h           |   4 +
> >  ovn-nb.xml                |  43 ++++++
> >  tests/multinode-macros.at |  48 +++++++
> >  tests/multinode.at        | 196 +++++++++++++++++++++++++++
> >  tests/ovn-controller.at   | 153 +++++++++++++++++++++
> >  tests/ovn-macros.at       |   1 +
> >  tests/ovn-northd.at       |  51 +++++++
> >  tests/ovn.at              |  10 +-
> >  tests/test-ovn.c          |   1 +
> >  utilities/ovn-trace.c     |   3 +
> >  19 files changed, 826 insertions(+), 66 deletions(-)
> >
> > --
> > 2.47.1
> >
> > _______________________________________________
> > dev mailing list
> > d...@openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-dev
> >
>
>
> --
> Quique Llorente
>
> CNV networking Senior Software Engineer
>
> Red Hat EMEA
>
> ellor...@redhat.com
>
> @RedHat   Red Hat  Red Hat
>

Thanks,
Ales
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to