> When putting an mbuf back into its mempool, there are certain requirements
> to the mbuf. Specifically, some of its fields must be initialized.
>
> These requirements are in fact invariants about free mbufs, held in
> mempools, and thus also apply when allocating an mbuf from a mempool.
> With
> From: Slava Ovsiienko [mailto:viachesl...@nvidia.com]
> Sent: Friday, 24 January 2025 11.23
>
> Acked-by: Viacheslav Ovsiienko
>
> PS. It seems we should consider replacing the rte_mempool_put_bulk()
> with the new wrapper rte_mbuf_fast_free_bulk() in the drivers.
Agree. And the individual dr
mas Monjalon (EXTERNAL) ;
> Ferruh Yigit ; Andrew Rybchenko
> ; Slava Ovsiienko
> ; Shahaf Shuler ; Olivier
> Matz
> Cc: dev@dpdk.org; Morten Brørup ; Dengdui
> Huang
> Subject: [PATCH v3] mbuf: add fast free bulk and raw alloc bulk functions
>
> When putting an mbuf b
LGTM
Acked-by: Chengwen Feng
On 2025/1/21 21:40, Morten Brørup wrote:
> When putting an mbuf back into its mempool, there are certain requirements
> to the mbuf. Specifically, some of its fields must be initialized.
>
> These requirements are in fact invariants about free mbufs, held in
> mempoo
When putting an mbuf back into its mempool, there are certain requirements
to the mbuf. Specifically, some of its fields must be initialized.
These requirements are in fact invariants about free mbufs, held in
mempools, and thus also apply when allocating an mbuf from a mempool.
With this in mind,
5 matches
Mail list logo
