From: Thomas Monjalon <thomas@monjalon.net>
To: Nitin Saxena <nsaxena16@gmail.com>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Robin Jarry <rjarry@redhat.com>,
Christophe Fontaine <cfontain@redhat.com>,
dev@dpdk.org, dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH v6 0/2] node: add mbuf dynamic field for nodes
Date: Wed, 11 Jun 2025 13:45:16 +0200 [thread overview]
Message-ID: <8151763.UjTJXf6HLC@thomas> (raw)
In-Reply-To: <20250428103711.3317231-1-nsaxena@marvell.com>
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
prev parent reply other threads:[~2025-06-11 11:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 4:20 [PATCH " Nitin Saxena
2025-04-01 4:20 ` [PATCH 1/2] node: add global node mbuf dynfield Nitin Saxena
2025-04-01 14:15 ` Stephen Hemminger
2025-04-03 10:27 ` Nitin Saxena
2025-04-04 8:11 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-04-04 15:21 ` Stephen Hemminger
2025-04-07 6:01 ` Nitin Saxena
2025-04-01 4:20 ` [PATCH 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena
2025-04-03 10:17 ` [PATCH v2 0/2] node: add mbuf dynamic field for nodes Nitin Saxena
2025-04-03 10:17 ` [PATCH v2 1/2] node: add global node mbuf dynfield Nitin Saxena
2025-04-03 10:17 ` [PATCH v2 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena
2025-04-04 7:12 ` [PATCH v3 0/2] node: add mbuf dynamic field for nodes Nitin Saxena
2025-04-04 7:12 ` [PATCH v3 1/2] node: add global node mbuf dynfield Nitin Saxena
2025-04-04 21:35 ` Stephen Hemminger
2025-04-04 7:12 ` [PATCH v3 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena
2025-04-07 7:47 ` [PATCH v4 0/2] node: add mbuf dynamic field for nodes Nitin Saxena
2025-04-07 7:47 ` [PATCH v4 1/2] node: add global node mbuf dynfield Nitin Saxena
2025-04-07 7:47 ` [PATCH v4 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena
2025-04-08 7:35 ` [PATCH v4 0/2] node: add mbuf dynamic field for nodes David Marchand
2025-04-08 8:42 ` Nitin Saxena
2025-04-09 13:55 ` [PATCH v5 " Nitin Saxena
2025-04-09 13:55 ` [PATCH v5 1/2] node: add global node mbuf dynfield Nitin Saxena
2025-04-18 19:03 ` Pavan Nikhilesh Bhagavatula
2025-04-28 10:42 ` Nitin Saxena
2025-04-09 13:55 ` [PATCH v5 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena
2025-04-28 10:37 ` [PATCH v6 0/2] node: add mbuf dynamic field for nodes Nitin Saxena
2025-04-28 10:37 ` [PATCH v6 1/2] node: add global node mbuf dynfield Nitin Saxena
2025-05-09 7:16 ` Pavan Nikhilesh Bhagavatula
2025-04-28 10:37 ` [PATCH v6 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena
2025-05-09 7:17 ` Pavan Nikhilesh Bhagavatula
2025-05-05 17:20 ` [PATCH v6 0/2] node: add mbuf dynamic field for nodes Pavan Nikhilesh Bhagavatula
2025-06-11 11:45 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8151763.UjTJXf6HLC@thomas \
--to=thomas@monjalon.net \
--cc=cfontain@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=nsaxena16@gmail.com \
--cc=pbhagavatula@marvell.com \
--cc=rjarry@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).