Hi Thomas,

Thanks,
Nitin

On Wed, Jun 11, 2025 at 5:15 PM Thomas Monjalon <tho...@monjalon.net> wrote:
>
> 28/04/2025 12:37, Nitin Saxena:
> > Currently each rte_node registers separate mbuf dynamic fields for their
> > own purpose. This leads to wastage of mbuf space as once mbuf get passed
> > a particular node, the registered dynamic field(by that node) is no
> > longer used.
> >
> > This patch series adds a global/common mbuf dynamic field which is
> > reusable by all the nodes(including out-of-tree nodes). This helps to
> > repurpose same mbuf dynamic field for other nodes. It contains two types
> > of fields: (a) persistent (b) overloadable.
> >
> > While persistent fields are those which does not often changes during a
> > graph walk such as rx/tx interface, buffer flags etc. Currently there
> > are no persistent fields added but they can be added later
> >
> > Overloadable fields are those which can be used by two adjacent nodes.
> > Same overloadable fields can be repurposed by other two adjacent nodes.
> >
> > This patch series also updates ip4/ip6 lookup/rewrite nodes to use
> > overlaodable mbuf dynamic fields.
> >
> > Changes in v6:
> > - Incorporate comments from Pavan
> >
> > Changes in v5
> > - Rebase on latest main with version.map changes
> > - Bring back memzone based node mbuf dynfield for secondary
> >   process [Pavan]
>
> Please it needs to be rebased again on top of feature arc that you added.
> Thanks

Rebased patch-set v7 on top of main. Sorry could not do earlier
>
>

Reply via email to