From: Akhil Goyal <gakhil@marvell.com>
To: <dev@dpdk.org>
Cc: <anoobj@marvell.com>, <thomas@monjalon.net>,
<ferruh.yigit@intel.com>, <andrew.rybchenko@oktetlabs.ru>,
<jerinj@marvell.com>, <ndabilpuram@marvell.com>,
<vvelumuri@marvell.com>, <pbhagavatula@marvell.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: [PATCH v5 0/2] net/cnxk: support IP reassembly offload
Date: Thu, 24 Feb 2022 23:58:59 +0530 [thread overview]
Message-ID: <20220224182901.4050206-1-gakhil@marvell.com> (raw)
In-Reply-To: <20220224172807.4028321-1-gakhil@marvell.com>
cn10k platform can support IP reassembly offload for upto 4 fragments
in the inline IPsec path.
The feature is enabled and tested as per unit test app[1].
The patchset is rebased over [2].
[1]: http://patchwork.dpdk.org/user/todo/dpdk/?series=21716
[2]: https://patches.dpdk.org/project/dpdk/list/?series=21874
Changes in v5:
- added release notes
- fixed checkpatch warnings. COMPLEX_MACRO issues are left
intentionally.
- reword commit message.
Changes in v4:
- refactor reassembly function pointers/defines so that new files are
not needed.
- handled Jerin's comment
- rebased over [2] and over next-net-mrvl.
Changes in v3:
- 3rd and 4th patch of the series are separated out.
- rebased over a dependent series.
changes in v2:
- updated as per changes in ethdev patches
- dynflags and dynfield for incomplete reassembly are registered in a
single API
- squashed the patch for dynfield in the reassembly patch.
Vidya Sagar Velumuri (2):
common/cnxk: configure reassembly specific params
net/cnxk: support IP reassembly
doc/guides/rel_notes/release_22_03.rst | 1 +
drivers/common/cnxk/cnxk_security.c | 10 +
drivers/common/cnxk/roc_nix_inl.c | 23 +
drivers/common/cnxk/roc_nix_inl.h | 7 +
drivers/common/cnxk/version.map | 1 +
drivers/event/cnxk/cn10k_worker.h | 56 +-
drivers/event/cnxk/deq/cn10k/deq_0_15.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_0_15_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_0_15_ca.c | 4 +-
.../event/cnxk/deq/cn10k/deq_0_15_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_0_15_ca_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_0_15_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_0_15_ca_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_0_15_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_0_15_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_0_15_ca_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_0_15_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_0_15_seg.c | 4 +-
.../event/cnxk/deq/cn10k/deq_0_15_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_0_15_tmo.c | 4 +-
.../event/cnxk/deq/cn10k/deq_0_15_tmo_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_0_15_tmo_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_0_15_tmo_seg_burst.c | 2 +-
drivers/event/cnxk/deq/cn10k/deq_112_127.c | 4 +-
.../event/cnxk/deq/cn10k/deq_112_127_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_112_127_ca.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_112_127_ca_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_112_127_ca_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_112_127_ca_tmo_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_112_127_dual.c | 4 +-
.../event/cnxk/deq/cn10k/deq_112_127_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_112_127_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_112_127_tmo_seg.c | 4 +-
.../deq/cn10k/deq_112_127_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_16_31.c | 4 +-
.../event/cnxk/deq/cn10k/deq_16_31_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_16_31_ca.c | 4 +-
.../event/cnxk/deq/cn10k/deq_16_31_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_16_31_ca_seg.c | 5 +-
.../cnxk/deq/cn10k/deq_16_31_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_16_31_ca_tmo.c | 5 +-
.../cnxk/deq/cn10k/deq_16_31_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_16_31_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_16_31_ca_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_16_31_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_16_31_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_16_31_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_16_31_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_16_31_tmo_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_16_31_tmo_seg.c | 5 +-
.../cnxk/deq/cn10k/deq_16_31_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_32_47.c | 4 +-
.../event/cnxk/deq/cn10k/deq_32_47_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_32_47_ca.c | 4 +-
.../event/cnxk/deq/cn10k/deq_32_47_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_32_47_ca_seg.c | 5 +-
.../cnxk/deq/cn10k/deq_32_47_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_32_47_ca_tmo.c | 5 +-
.../cnxk/deq/cn10k/deq_32_47_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_32_47_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_32_47_ca_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_32_47_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_32_47_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_32_47_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_32_47_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_32_47_tmo_burst.c | 5 +-
.../event/cnxk/deq/cn10k/deq_32_47_tmo_seg.c | 5 +-
.../cnxk/deq/cn10k/deq_32_47_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_48_63.c | 4 +-
.../event/cnxk/deq/cn10k/deq_48_63_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_48_63_ca.c | 4 +-
.../event/cnxk/deq/cn10k/deq_48_63_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_48_63_ca_seg.c | 5 +-
.../cnxk/deq/cn10k/deq_48_63_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_48_63_ca_tmo.c | 5 +-
.../cnxk/deq/cn10k/deq_48_63_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_48_63_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_48_63_ca_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_48_63_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_48_63_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_48_63_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_48_63_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_48_63_tmo_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_48_63_tmo_seg.c | 5 +-
.../cnxk/deq/cn10k/deq_48_63_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_64_79.c | 4 +-
.../event/cnxk/deq/cn10k/deq_64_79_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_64_79_ca.c | 4 +-
.../event/cnxk/deq/cn10k/deq_64_79_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_64_79_ca_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_64_79_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_64_79_ca_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_64_79_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_64_79_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_64_79_ca_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_64_79_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_64_79_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_64_79_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_64_79_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_64_79_tmo_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_64_79_tmo_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_64_79_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_80_95.c | 4 +-
.../event/cnxk/deq/cn10k/deq_80_95_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_80_95_ca.c | 4 +-
.../event/cnxk/deq/cn10k/deq_80_95_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_80_95_ca_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_80_95_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_80_95_ca_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_80_95_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_80_95_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_80_95_ca_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_80_95_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_80_95_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_80_95_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_80_95_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_80_95_tmo_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_80_95_tmo_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_80_95_tmo_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_96_111.c | 4 +-
.../event/cnxk/deq/cn10k/deq_96_111_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_96_111_ca.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_ca_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_96_111_ca_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_ca_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_96_111_ca_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_ca_tmo_burst.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_ca_tmo_seg.c | 4 +-
.../deq/cn10k/deq_96_111_ca_tmo_seg_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_96_111_dual.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_96_111_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_seg_burst.c | 4 +-
drivers/event/cnxk/deq/cn10k/deq_96_111_tmo.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_tmo_burst.c | 4 +-
.../event/cnxk/deq/cn10k/deq_96_111_tmo_seg.c | 4 +-
.../cnxk/deq/cn10k/deq_96_111_tmo_seg_burst.c | 4 +-
drivers/net/cnxk/cn10k_ethdev.c | 51 ++
drivers/net/cnxk/cn10k_ethdev.h | 2 +
drivers/net/cnxk/cn10k_ethdev_sec.c | 13 +
drivers/net/cnxk/cn10k_rx.h | 566 ++++++++++++++++--
drivers/net/cnxk/cn10k_rx_select.c | 54 +-
drivers/net/cnxk/cnxk_ethdev.h | 4 +
drivers/net/cnxk/rx/cn10k/rx_0_15.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_0_15_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_0_15_vec.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_0_15_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_112_127.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_112_127_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_112_127_vec.c | 4 +-
.../net/cnxk/rx/cn10k/rx_112_127_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_16_31.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_16_31_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_16_31_vec.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_16_31_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_32_47.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_32_47_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_32_47_vec.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_32_47_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_48_63.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_48_63_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_48_63_vec.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_48_63_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_64_79.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_64_79_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_64_79_vec.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_64_79_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_80_95.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_80_95_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_80_95_vec.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_80_95_vec_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_96_111.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_96_111_mseg.c | 4 +-
drivers/net/cnxk/rx/cn10k/rx_96_111_vec.c | 4 +-
.../net/cnxk/rx/cn10k/rx_96_111_vec_mseg.c | 4 +-
180 files changed, 1238 insertions(+), 230 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2022-02-24 18:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:01 [PATCH 0/5] " Akhil Goyal
2022-01-03 16:01 ` [PATCH 1/5] common/cnxk: configure reassembly specific params Akhil Goyal
2022-01-03 16:01 ` [PATCH 2/5] net/cnxk: reassembly support Akhil Goyal
2022-01-03 16:01 ` [PATCH 3/5] net/cnxk: support IP reassembly mbuf dynfield Akhil Goyal
2022-01-03 16:01 ` [PATCH 4/5] net/cnxk: add dev args for min-max spi Akhil Goyal
2022-01-03 16:01 ` [PATCH 5/5] net/cnxk: add option to override outbound inline sa iv Akhil Goyal
2022-01-20 16:53 ` [PATCH v2 0/4] net/cnxk: support IP reassembly offload Akhil Goyal
2022-01-20 16:53 ` [PATCH v2 1/4] common/cnxk: configure reassembly specific params Akhil Goyal
2022-01-20 16:53 ` [PATCH v2 2/4] net/cnxk: support IP reassembly Akhil Goyal
2022-01-20 16:53 ` [PATCH v2 3/4] net/cnxk: add dev args for min-max spi Akhil Goyal
2022-01-20 16:53 ` [PATCH v2 4/4] net/cnxk: add option to override outbound inline sa iv Akhil Goyal
2022-02-23 12:28 ` [PATCH v3 0/2] net/cnxk: support IP reassembly offload Akhil Goyal
2022-02-23 12:28 ` [PATCH v3 1/2] common/cnxk: configure reassembly specific params Akhil Goyal
2022-02-23 16:51 ` Jerin Jacob
2022-02-23 12:28 ` [PATCH v3 2/2] net/cnxk: support IP reassembly Akhil Goyal
2022-02-23 16:57 ` Jerin Jacob
2022-02-24 17:28 ` [PATCH v4 0/2] net/cnxk: support IP reassembly offload Akhil Goyal
2022-02-24 17:28 ` [PATCH v4 1/2] common/cnxk: configure reassembly specific params Akhil Goyal
2022-02-24 17:28 ` [PATCH v4 2/2] net/cnxk: support IP reassembly Akhil Goyal
2022-02-24 17:41 ` Jerin Jacob
2022-02-24 18:28 ` Akhil Goyal [this message]
2022-02-24 18:29 ` [PATCH v5 1/2] common/cnxk: configure reassembly specific params Akhil Goyal
2022-02-24 18:29 ` [PATCH v5 2/2] net/cnxk: support IP reassembly Akhil Goyal
2022-02-24 20:40 ` [PATCH v5 0/2] net/cnxk: support IP reassembly offload Jerin Jacob
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=20220224182901.4050206-1-gakhil@marvell.com \
--to=gakhil@marvell.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=thomas@monjalon.net \
--cc=vvelumuri@marvell.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).