From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ankur Dwivedi <adwivedi@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: fix buffer size assignment
Date: Thu, 21 May 2020 15:48:54 +0530 [thread overview]
Message-ID: <CALBAE1P5JbQ=MbuQJuYP1kebcN+y43WjTkasCyEOTvkskx9AjA@mail.gmail.com> (raw)
In-Reply-To: <1589977210-31046-1-git-send-email-adwivedi@marvell.com>
On Wed, May 20, 2020 at 5:51 PM Ankur Dwivedi <adwivedi@marvell.com> wrote:
>
> The elt_size field in mempool holds the size of one packet buffer.
> It can be used to set the lpm_sizem1 field in rq context.
>
> The lpb_sizem1 field in rq context is 12 bit, direct assignment
> to it was causing overflow of value. Because of this errors
> were observed while trying inline inbound with large packets.
> This patch resolves the errors.
>
> Fixes: 094fc8a3a1e2 ("net/octeontx2: add Rx queue setup and release")
Cc: stable@dpdk.org
>
> Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com>
> Reviewed-by: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
> Reviewed-by: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Fixed the name and Applied to dpdk-next-net-mrvl/master. Thanks
> ---
> drivers/net/octeontx2/otx2_ethdev.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/net/octeontx2/otx2_ethdev.c b/drivers/net/octeontx2/otx2_ethdev.c
> index 3116e5c..3f3f0a6 100644
> --- a/drivers/net/octeontx2/otx2_ethdev.c
> +++ b/drivers/net/octeontx2/otx2_ethdev.c
> @@ -373,10 +373,7 @@
> aq->rq.first_skip = first_skip;
> aq->rq.later_skip = (sizeof(struct rte_mbuf) / 8);
> aq->rq.flow_tagw = 32; /* 32-bits */
> - aq->rq.lpb_sizem1 = rte_pktmbuf_data_room_size(mp);
> - aq->rq.lpb_sizem1 += rte_pktmbuf_priv_size(mp);
> - aq->rq.lpb_sizem1 += sizeof(struct rte_mbuf);
> - aq->rq.lpb_sizem1 /= 8;
> + aq->rq.lpb_sizem1 = mp->elt_size / 8;
> aq->rq.lpb_sizem1 -= 1; /* Expressed in size minus one */
> aq->rq.ena = 1;
> aq->rq.pb_caching = 0x2; /* First cache aligned block to LLC */
> --
> 1.9.3
>
prev parent reply other threads:[~2020-05-21 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 12:20 Ankur Dwivedi
2020-05-21 10:18 ` Jerin Jacob [this message]
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='CALBAE1P5JbQ=MbuQJuYP1kebcN+y43WjTkasCyEOTvkskx9AjA@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=adwivedi@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@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).