From: Ashwin Sekhar T K <asekhar@marvell.com>
To: Rakesh Kudurumalla <rkudurumalla@marvell.com>,
Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Rakesh Kudurumalla <rkudurumalla@marvell.com>
Subject: RE: [EXT] [PATCH 1/1] app/test: resolve mbuf_test application failure
Date: Tue, 4 Jul 2023 04:39:18 +0000 [thread overview]
Message-ID: <CO1PR18MB454090F595C721C3CD83CDD1BF2EA@CO1PR18MB4540.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230426092750.2423850-1-rkudurumalla@marvell.com>
Acked-by: Ashwin Sekhar T K <asekhar@marvell.com>
Ashwin Sekhar T K
> -----Original Message-----
> From: Rakesh Kudurumalla <rkudurumalla@marvell.com>
> Sent: Wednesday, April 26, 2023 2:58 PM
> To: Olivier Matz <olivier.matz@6wind.com>
> Cc: dev@dpdk.org; Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin
> Kumar Dabilpuram <ndabilpuram@marvell.com>; Rakesh Kudurumalla
> <rkudurumalla@marvell.com>
> Subject: [EXT] [PATCH 1/1] app/test: resolve mbuf_test application failure
>
> External Email
>
> ----------------------------------------------------------------------
> when RTE_ENABLE_ASSERT is defined test_mbuf application is failing
> because we are trying to attach extbuf to a cloned buffer to which external
> mbuf is already attached.This patch fixes the same.
>
> Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
> ---
> v2: removed gerrit id
>
> app/test/test_mbuf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/app/test/test_mbuf.c b/app/test/test_mbuf.c index
> 8d8d3b9386..e2b81db308 100644
> --- a/app/test/test_mbuf.c
> +++ b/app/test/test_mbuf.c
> @@ -2375,6 +2375,7 @@ test_pktmbuf_ext_shinfo_init_helper(struct
> rte_mempool *pktmbuf_pool)
> GOTO_FAIL("%s: Bad packet length\n", __func__);
>
> /* attach the same external buffer to the cloned mbuf */
> + clone->ol_flags = 0;
> rte_pktmbuf_attach_extbuf(clone, ext_buf_addr, buf_iova,
> buf_len,
> ret_shinfo);
> if (clone->ol_flags != RTE_MBUF_F_EXTERNAL)
> --
> 2.25.1
next prev parent reply other threads:[~2023-07-04 4:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 9:23 Rakesh Kudurumalla
2023-04-26 9:27 ` Rakesh Kudurumalla
2023-05-23 15:39 ` Rakesh Kudurumalla
2023-07-05 16:12 ` Olivier Matz
2023-07-24 6:27 ` [EXT] " Rakesh Kudurumalla
2023-07-04 4:39 ` Ashwin Sekhar T K [this message]
2023-07-26 5:55 ` [PATCH v2 " Rakesh Kudurumalla
2023-10-03 4:20 ` Rakesh Kudurumalla
2023-10-17 13:18 ` Olivier Matz
2023-11-23 6:42 ` [PATCH v3 1/1] app/test: fix external mbuf test when assertions enabled Rakesh Kudurumalla
2024-03-06 17:37 ` 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=CO1PR18MB454090F595C721C3CD83CDD1BF2EA@CO1PR18MB4540.namprd18.prod.outlook.com \
--to=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=rkudurumalla@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).