From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: dev@dpdk.org
Subject: [PATCH 0/4] pipeline: support large structure fields
Date: Fri, 12 Aug 2022 09:54:41 +0000 [thread overview]
Message-ID: <20220812095445.1253138-1-cristian.dumitrescu@intel.com> (raw)
This patch set adds support for structure fields bigger than 64 bits.
These fields can be packet header or meta-data fields. They can be
used as part of the table lookup key or as action arguments. They are
now valid operands for the move instruction.
This is required for supporting the 128-bit IPv6 addresses, which up
to now had to be split into two 64-bit fields.
Cristian Dumitrescu (4):
pipeline: remove the 64-bit limit for structure fields
pipeline: read large structure fields on the control path
pipeline: support large default action arguments
pipeline: add instruction support for moving large structure fields
lib/pipeline/rte_swx_ctl.c | 357 +++++++++++++++++++----
lib/pipeline/rte_swx_pipeline.c | 256 +++++++++++-----
lib/pipeline/rte_swx_pipeline_internal.h | 78 ++++-
lib/pipeline/rte_swx_pipeline_spec.c | 3 +-
4 files changed, 559 insertions(+), 135 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-12 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 9:54 Cristian Dumitrescu [this message]
2022-08-12 9:54 ` [PATCH 1/4] pipeline: remove the 64-bit limit for " Cristian Dumitrescu
2022-08-12 9:54 ` [PATCH 2/4] pipeline: read large structure fields on the control path Cristian Dumitrescu
2022-08-12 9:54 ` [PATCH 3/4] pipeline: support large default action arguments Cristian Dumitrescu
2022-08-12 9:54 ` [PATCH 4/4] pipeline: add instruction support for moving large structure fields Cristian Dumitrescu
2022-09-23 11:56 ` [PATCH 0/4] pipeline: support " Thomas Monjalon
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=20220812095445.1253138-1-cristian.dumitrescu@intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
/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).