From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: free CQ ring memzone on queue release
Date: Tue, 21 Jul 2020 17:39:02 +0530 [thread overview]
Message-ID: <CALBAE1OiD8ZEjt3E8TjDZduxP=i5-tmxX2E=BKiobdOp1nQt7A@mail.gmail.com> (raw)
In-Reply-To: <20200628233136.2953-1-pbhagavatula@marvell.com>
On Mon, Jun 29, 2020 at 5:03 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Free CQ ring memzone on Rx queue release. This prevents CQ using
> incorrect memory size when ring size is reconfigured.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> This patch depends on the following patch
> http://patches.dpdk.org/patch/72035/
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks
>
> drivers/net/octeontx2/otx2_ethdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/octeontx2/otx2_ethdev.c b/drivers/net/octeontx2/otx2_ethdev.c
> index 3f3f0a693..a1084bf96 100644
> --- a/drivers/net/octeontx2/otx2_ethdev.c
> +++ b/drivers/net/octeontx2/otx2_ethdev.c
> @@ -528,6 +528,7 @@ otx2_nix_rx_queue_setup(struct rte_eth_dev *eth_dev, uint16_t rq,
> if (eth_dev->data->rx_queues[rq] != NULL) {
> otx2_nix_dbg("Freeing memory prior to re-allocation %d", rq);
> otx2_nix_rx_queue_release(eth_dev->data->rx_queues[rq]);
> + rte_eth_dma_zone_free(eth_dev, "cq", rq);
> eth_dev->data->rx_queues[rq] = NULL;
> }
>
> --
> 2.17.1
>
prev parent reply other threads:[~2020-07-21 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 23:31 pbhagavatula
2020-07-21 12:09 ` 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='CALBAE1OiD8ZEjt3E8TjDZduxP=i5-tmxX2E=BKiobdOp1nQt7A@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@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).