From: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2] kni: optimize alloc queue release
Date: Wed, 13 Apr 2022 10:23:30 +0000 [thread overview]
Message-ID: <MW4PR11MB59117B575C0CA4216AA4D44A87EC9@MW4PR11MB5911.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220413054856.3054752-1-s.v.naga.harish.k@intel.com>
Hi Harish
> -----Original Message-----
> From: Naga Harish K S V <s.v.naga.harish.k@intel.com>
> Sent: 13 April 2022 11:19
> To: Yigit, Ferruh <ferruh.yigit@intel.com>
> Cc: Jayatheerthan, Jay <jay.jayatheerthan@intel.com>; dev@dpdk.org
> Subject: [PATCH v2] kni: optimize alloc queue release
>
> the kni alloc queue is filled with physical addresses of mbufs for kernel
> consumption. Any unused mbufs in the alloc queue are freed during
> shutdown sequence in rte_kni_release.
>
> In the current existing implementation, for freeing one entry of alloc queue
> all the objects of the mempool are traversed. This process is repeated for all
> the objects of the alloc queue which consumes lot of cpu cycles.
>
> Instead of using mempool object iteration method,use
> ``rte_mem_iova2virt()`` api to get the virtual address for the physical
> addresses of alloc_q objects.
> This sppeds up the freeing process.
Nitpick: speeds
>
> Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
> ---
> v2:
> * fix checkpatch errors
> ---
> lib/kni/rte_kni.c | 23 ++++++++---------------
> 1 file changed, 8 insertions(+), 15 deletions(-)
>
> diff --git a/lib/kni/rte_kni.c b/lib/kni/rte_kni.c index 7971c56bb4..f443e5b2fc
> 100644
> --- a/lib/kni/rte_kni.c
> +++ b/lib/kni/rte_kni.c
> @@ -375,26 +375,19 @@ va2pa_all(struct rte_mbuf *mbuf) }
>
> static void
> -obj_free(struct rte_mempool *mp __rte_unused, void *opaque, void *obj,
> - unsigned obj_idx __rte_unused)
> -{
> - struct rte_mbuf *m = obj;
> - void *mbuf_phys = opaque;
> -
> - if (va2pa(m) == mbuf_phys)
> - rte_pktmbuf_free(m);
> -}
> -
> -static void
> -kni_free_fifo_phy(struct rte_mempool *mp, struct rte_kni_fifo *fifo)
> +kni_free_fifo_phy(struct rte_kni_fifo *fifo)
> {
> void *mbuf_phys;
> int ret;
> + struct rte_mbuf *m;
>
> do {
> ret = kni_fifo_get(fifo, &mbuf_phys, 1);
> - if (ret)
> - rte_mempool_obj_iter(mp, obj_free, mbuf_phys);
> + if (ret) {
> + m = (struct rte_mbuf *)
> + rte_mem_iova2virt((rte_iova_t)mbuf_phys);
> + rte_pktmbuf_free(m);
> + }
> } while (ret);
> }
>
> @@ -440,7 +433,7 @@ rte_kni_release(struct rte_kni *kni)
> if (kni_fifo_count(kni->rx_q))
> RTE_LOG(ERR, KNI, "Fail to free all Rx-q items\n");
>
> - kni_free_fifo_phy(kni->pktmbuf_pool, kni->alloc_q);
> + kni_free_fifo_phy(kni->alloc_q);
> kni_free_fifo(kni->tx_q);
> kni_free_fifo(kni->free_q);
>
> --
> 2.23.0
next prev parent reply other threads:[~2022-04-13 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 5:40 [PATCH] " Naga Harish K S V
2022-04-13 5:48 ` [PATCH v2] " Naga Harish K S V
2022-04-13 10:23 ` Kundapura, Ganapati [this message]
2022-04-14 10:01 ` Naga Harish K, S V
2022-04-13 14:57 ` [PATCH v3] " Naga Harish K S V
2022-04-14 15:20 ` Jayatheerthan, Jay
2022-04-14 17:38 ` Naga Harish K, S V
2022-04-14 17:35 ` [PATCH v4] " Naga Harish K S V
2022-05-31 8:32 ` Naga Harish K, S V
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=MW4PR11MB59117B575C0CA4216AA4D44A87EC9@MW4PR11MB5911.namprd11.prod.outlook.com \
--to=ganapati.kundapura@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=s.v.naga.harish.k@intel.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).