From: Rahul Bhansali <rbhansali@marvell.com>
To: <dev@dpdk.org>, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>
Cc: <jerinj@marvell.com>, Rahul Bhansali <rbhansali@marvell.com>
Subject: [PATCH v2 5/5] net/cnxk: add mempool check for frag attach
Date: Thu, 18 May 2023 21:19:02 +0530 [thread overview]
Message-ID: <20230518154902.2254743-5-rbhansali@marvell.com> (raw)
In-Reply-To: <20230518154902.2254743-1-rbhansali@marvell.com>
Add mempool cookies get mark to all frags in case of
reassembly failure.
Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
---
Changes in v2: No change
drivers/net/cnxk/cn10k_rx.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/net/cnxk/cn10k_rx.h b/drivers/net/cnxk/cn10k_rx.h
index 9fdb5565e9..cbaf994aa2 100644
--- a/drivers/net/cnxk/cn10k_rx.h
+++ b/drivers/net/cnxk/cn10k_rx.h
@@ -211,6 +211,9 @@ nix_sec_attach_frags(const struct cpt_parse_hdr_s *hdr,
/* Update dynamic field with userdata */
*rte_security_dynfield(mbuf) = (uint64_t)inb_priv->userdata;
+ /* Mark frag as get */
+ RTE_MEMPOOL_CHECK_COOKIES(mbuf->pool, (void **)&mbuf, 1, 1);
+
cnxk_ip_reassembly_dynfield(mbuf, off)->nb_frags =
hdr->w0.num_frags - 2;
cnxk_ip_reassembly_dynfield(mbuf, off)->next_frag = NULL;
@@ -239,6 +242,9 @@ nix_sec_attach_frags(const struct cpt_parse_hdr_s *hdr,
/* Update dynamic field with userdata */
*rte_security_dynfield(mbuf) = (uint64_t)inb_priv->userdata;
+ /* Mark frag as get */
+ RTE_MEMPOOL_CHECK_COOKIES(mbuf->pool, (void **)&mbuf, 1, 1);
+
cnxk_ip_reassembly_dynfield(mbuf, off)->nb_frags =
hdr->w0.num_frags - 3;
cnxk_ip_reassembly_dynfield(mbuf, off)->next_frag = NULL;
@@ -263,6 +269,9 @@ nix_sec_attach_frags(const struct cpt_parse_hdr_s *hdr,
mbuf->ol_flags = ol_flags;
mbuf->next = NULL;
+ /* Mark frag as get */
+ RTE_MEMPOOL_CHECK_COOKIES(mbuf->pool, (void **)&mbuf, 1, 1);
+
/* Update dynamic field with userdata */
*rte_security_dynfield(mbuf) = (uint64_t)inb_priv->userdata;
--
2.25.1
next prev parent reply other threads:[~2023-05-18 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 10:40 [PATCH 1/5] common/cnxk: fix IPsec IPv6 tunnel address byte swap Rahul Bhansali
2023-04-25 10:40 ` [PATCH 2/5] event/cnxk: set Rx offload flags Rahul Bhansali
2023-04-25 10:40 ` [PATCH 3/5] event/cnxk: fix Tx adapter data pointer Rahul Bhansali
2023-04-25 10:40 ` [PATCH 4/5] event/cnxk: fix mempool cookies check Rahul Bhansali
2023-04-25 10:40 ` [PATCH 5/5] net/cnxk: add mempool check for frag attach Rahul Bhansali
2023-05-18 6:31 ` [PATCH 1/5] common/cnxk: fix IPsec IPv6 tunnel address byte swap Jerin Jacob
2023-05-18 15:48 ` [PATCH v2 " Rahul Bhansali
2023-05-18 15:48 ` [PATCH v2 2/5] event/cnxk: set Rx offload flags Rahul Bhansali
2023-05-18 15:49 ` [PATCH v2 3/5] event/cnxk: fix Tx adapter data pointer Rahul Bhansali
2023-05-18 15:49 ` [PATCH v2 4/5] event/cnxk: fix mempool cookies check Rahul Bhansali
2023-05-18 15:49 ` Rahul Bhansali [this message]
2023-05-22 13:14 ` [PATCH v2 5/5] net/cnxk: add mempool check for frag attach 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=20230518154902.2254743-5-rbhansali@marvell.com \
--to=rbhansali@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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).