On Wed, 25 Feb 2026 at 12:04, David Marchand via dev
<[email protected]> wrote:
>
> By default, DPDK based dp-packets points to data buffers that can't be
> expanded dynamically.
> Their layout is as follows:
> - a minimum 128 bytes headroom chosen at DPDK build time
>   (RTE_PKTMBUF_HEADROOM),
> - a maximum size chosen at mempool creation,
>
> In some usecases though (like encapsulating with multiple tunnels),
> a 128 bytes headroom is too short.
>
> Keep on using mono segment packets but dynamically allocate buffers
> in DPDK memory and make use of DPDK external buffers API
> (previously used for userspace TSO).
>
> Signed-off-by: David Marchand <[email protected]>

Here is a strange failure in Cirrus CI (unrelated to the patch afaict).
Any idea what it could be? Some race?

487: ovs-ofctl replace-flows with --bundle FAILED (ovs-ofctl.at:3438)

./ovs-ofctl.at:3438: print_vconn_debug | vconn_sub | ofctl_strip
--- - 2026-02-25 11:59:36.400451000 +0000
+++ /tmp/cirrus-ci-build/tests/testsuite.dir/at-groups/487/stdout
2026-02-25 11:59:36.399629000 +0000
@@ -39,9 +39,9 @@
bundle_id=0 type=COMMIT_REPLY flags=0
vconn|DBG|unix: sent (Success): OFPT_HELLO (OF1.5):
version bitmap: 0x01, 0x02, 0x03, 0x04, 0x05, 0x06
+vconn|DBG|unix: negotiated OpenFlow version 0x05 (we support version
0x06 and earlier, peer supports version 0x05)
vconn|DBG|unix: received: OFPT_HELLO (OF1.4):
version bitmap: 0x05
-vconn|DBG|unix: negotiated OpenFlow version 0x05 (we support version
0x06 and earlier, peer supports version 0x05)
vconn|DBG|unix: received: OFPST_FLOW request (OF1.4):
vconn|DBG|unix: sent (Success): OFPST_FLOW reply (OF1.4):
table=1, importance=1, dl_vlan=1 actions=drop


-- 
David Marchand

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

Reply via email to