On Wed, 1 Jul 2026 at 14:24, David Marchand <[email protected]> wrote:
> > Programs that do not need datapath functionality now link only
> > libopenvswitchutils, reducing their dependency footprint:
> > ovsdb-server, ovsdb-client, ovsdb-tool, ovs-appctl, vtep-ctl.
> >
> > To break a circular dependency between the two libraries,
> > ip_parse(), ipv6_parse(), and ipv6_string_mapped() are made
> > static inline in packets.h.  These are trivial wrappers around
> > inet_pton()/inet_ntop() with no side effects or state.
> >
> > Signed-off-by: Timothy Redaelli <[email protected]>
> > ---
> > Changes since v4:
> >   - Squashed into a single patch.
> >   - Dropped net-proto rename per Ilya's review: keep packets.c/h
> >     as-is, no new net-proto.c/h files.
> >   - Dropped pop_mpls and other function moves to dp-packet per
> >     Ilya's review.
> >   - Inlined ip_parse(), ipv6_parse(), ipv6_string_mapped() in
> >     packets.h to resolve cross-library dependency (trivial
> >     wrappers around inet_pton/inet_ntop).
> >   - Fixed shared library builds: link libopenvswitchutils.la
> >     explicitly in every executable that also links libopenvswitch.la
> >     (utilities, vswitchd, tests, oss-fuzz), so the directly
> >     referenced utils symbols resolve under --enable-shared.
> >   - Fixed debian Python extension: link libopenvswitchutils
> >     instead of libopenvswitch.
> >   - Fixed sparse checker: include ordering in packets.h.
> >   - Kept the generated vswitch-idl in libopenvswitch (datapath and
> >     schema consumers); only dirs and ovsdb-server-idl moved to the
> >     libopenvswitchutils sources.
>
> Well, on this last point, that forces tools like ovs-vsctl to link
> against libopenvswitch which in turn pulls in dpdk.
> Are you still gaining space from this rework (asking, as I see no
> number in the commitlog)?
>
> Maybe this is enough as a first step.

It seems we can remove the dependency on test-lib too.


-- 
David Marchand

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to