Hi Robin,
vlib_buffer_enqueue_to_next is more optimized and simpler to use and most of
new features are using it.
vlib_{get,put}_next_frame is there for compatibility reasons, still many nodes
are using it.
--
Damjan
> On 29.03.2026., at 23:11, Robin Christ via lists.fd.io
> <[email protected]> wrote:
>
> Hey folks,
>
> I'm trying to figure out the difference between the "vlib_get_next_frame +
> vlib_put_next_frame + vlib_validate_buffer_enqueue_x*" pattern and the
> "vlib_buffer_enqueue_to_next" pattern.
>
> From what it seems, "vlib_buffer_enqueue_to_next" is the more modern and
> preffered.
>
> Is this correct? I couldn't really find any docs about this..
>
> When should which pattern be used, what are the Pros and Cons?
>
>
> Thanks,
> Robin Christ
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#26931): https://lists.fd.io/g/vpp-dev/message/26931
Mute This Topic: https://lists.fd.io/mt/118569760/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
