DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Nitin Saxena <nsaxena@marvell.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,  Jerin Jacob <jerinj@marvell.com>,
	Nitin Saxena <nsaxena16@gmail.com>
Subject: Re: [PATCH v4 0/2] node: add mbuf dynamic field for nodes
Date: Tue, 8 Apr 2025 09:35:40 +0200	[thread overview]
Message-ID: <CAJFAV8wW5GFzGHJpSM4dcfys54=PD+RfWCr7AsbUqZqf0RZhQg@mail.gmail.com> (raw)
In-Reply-To: <20250407074800.1651203-1-nsaxena@marvell.com>

Hello Nitin,

On Mon, Apr 7, 2025 at 9:48 AM Nitin Saxena <nsaxena@marvell.com> wrote:
>
> 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 overloaded by two adjacent
> nodes. 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 v4
> - Fix github CI
>
> Changes in v3:
> - Fix CI build error
>
> Changes in v2:
> - removed usage of memzone for saving mbuf dynfield [Stephen]
> - fixed checkpatch issues
> - redefine RTE_NODE_MBUF_OVERLOADABLE_FIELDS_SIZE to 8 byte which are
>   currently in use. Size can increase later based on the usage
>
>
> Nitin Saxena (2):
>   node: add global node mbuf dynfield
>   node: use node mbuf dynfield in ip4 nodes
>
>  doc/api/doxy-api-index.md              |   3 +-
>  doc/guides/rel_notes/release_25_07.rst |   6 ++
>  lib/node/ip4_lookup.c                  |  14 +--
>  lib/node/ip4_rewrite.c                 |  15 ++-
>  lib/node/ip6_lookup.c                  |  15 ++-
>  lib/node/ip6_rewrite.c                 |  14 +--
>  lib/node/meson.build                   |   2 +
>  lib/node/node_mbuf_dynfield.c          |  44 ++++++++
>  lib/node/node_private.h                |  40 +------
>  lib/node/rte_node_mbuf_dynfield.h      | 141 +++++++++++++++++++++++++
>  lib/node/version.map                   |   3 +

I did not review this series but I noticed some version.map update.

When pulling main, you'll notice that exporting symbols must be done
via RTE_EXPORT_*SYMBOL macros now.
No version.map touching anymore, those files are generated at build
time, so developers don't need to care about them.

In lib/node/node_mbuf_dynfield.c, you need to include eal_export.h and add:

+RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_node_mbuf_dynfield_register, 25.07)
+int rte_node_mbuf_dynfield_register(void)
+{
...


-- 
David Marchand


  parent reply	other threads:[~2025-04-08  7:35 UTC|newest]

Thread overview: 23+ 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   ` David Marchand [this message]
2025-04-08  8:42     ` [PATCH v4 0/2] node: add mbuf dynamic field for nodes 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-09 13:55   ` [PATCH v5 2/2] node: use node mbuf dynfield in ip4 nodes Nitin Saxena

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='CAJFAV8wW5GFzGHJpSM4dcfys54=PD+RfWCr7AsbUqZqf0RZhQg@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=cfontain@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=nsaxena16@gmail.com \
    --cc=nsaxena@marvell.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).