From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "xiaoyun.li@intel.com" <xiaoyun.li@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
"shepard.siegel@atomicrules.com" <shepard.siegel@atomicrules.com>,
"ed.czeck@atomicrules.com" <ed.czeck@atomicrules.com>,
"john.miller@atomicrules.com" <john.miller@atomicrules.com>,
Igor Russkikh <irusskikh@marvell.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"somnath.kotur@broadcom.com" <somnath.kotur@broadcom.com>,
"rahul.lakkireddy@chelsio.com" <rahul.lakkireddy@chelsio.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"sachin.saxena@oss.nxp.com" <sachin.saxena@oss.nxp.com>,
"haiyue.wang@intel.com" <haiyue.wang@intel.com>,
"johndale@cisco.com" <johndale@cisco.com>,
"hyonkim@cisco.com" <hyonkim@cisco.com>,
"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>,
"xiao.w.wang@intel.com" <xiao.w.wang@intel.com>,
"humin29@huawei.com" <humin29@huawei.com>,
"yisen.zhuang@huawei.com" <yisen.zhuang@huawei.com>,
"oulijun@huawei.com" <oulijun@huawei.com>,
"beilei.xing@intel.com" <beilei.xing@intel.com>,
"jingjing.wu@intel.com" <jingjing.wu@intel.com>,
"qiming.yang@intel.com" <qiming.yang@intel.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"viacheslavo@nvidia.com" <viacheslavo@nvidia.com>,
"sthemmin@microsoft.com" <sthemmin@microsoft.com>,
"longli@microsoft.com" <longli@microsoft.com>,
"heinrich.kuhn@corigine.com" <heinrich.kuhn@corigine.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
"Maciej Czekaj [C]" <mczekaj@marvell.com>,
"jiawenwu@trustnetic.com" <jiawenwu@trustnetic.com>,
"jianwang@trustnetic.com" <jianwang@trustnetic.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"chenbo.xia@intel.com" <chenbo.xia@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
"jay.jayatheerthan@intel.com" <jay.jayatheerthan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/7] ethdev: allocate max space for internal queue array
Date: Sat, 2 Oct 2021 00:02:04 +0000 [thread overview]
Message-ID: <PH0PR18MB4086A7C510E62F487A289A6CDEAC9@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
>At queue configure stage always allocate space for maximum possible
>number (RTE_MAX_QUEUES_PER_PORT) of queue pointers.
>That will allow 'fast' inline functions (eth_rx_burst, etc.) to refer
>pointer to internal queue data without extra checking of current
>number
>of configured queues.
>That would help in future to hide rte_eth_dev and related structures.
>
>Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>---
> lib/ethdev/rte_ethdev.c | 36 +++++++++---------------------------
> 1 file changed, 9 insertions(+), 27 deletions(-)
>
>diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
>index daf5ca9242..424bc260fa 100644
>--- a/lib/ethdev/rte_ethdev.c
>+++ b/lib/ethdev/rte_ethdev.c
>@@ -898,7 +898,8 @@ eth_dev_rx_queue_config(struct rte_eth_dev
>*dev, uint16_t nb_queues)
>
> if (dev->data->rx_queues == NULL && nb_queues != 0) { /*
>first time configuration */
> dev->data->rx_queues = rte_zmalloc("ethdev-
>>rx_queues",
>- sizeof(dev->data->rx_queues[0]) *
>nb_queues,
>+ sizeof(dev->data->rx_queues[0]) *
>+ RTE_MAX_QUEUES_PER_PORT,
> RTE_CACHE_LINE_SIZE);
> if (dev->data->rx_queues == NULL) {
> dev->data->nb_rx_queues = 0;
We could get rid of this zmalloc by declaring rx_queues as array of
pointers, it would make code much simpler.
I believe the original code dates back to "Initial" release.
>@@ -909,21 +910,11 @@ eth_dev_rx_queue_config(struct
>rte_eth_dev *dev, uint16_t nb_queues)
>
> rxq = dev->data->rx_queues;
>
>- for (i = nb_queues; i < old_nb_queues; i++)
>+ for (i = nb_queues; i < old_nb_queues; i++) {
> (*dev->dev_ops->rx_queue_release)(rxq[i]);
>- rxq = rte_realloc(rxq, sizeof(rxq[0]) * nb_queues,
>- RTE_CACHE_LINE_SIZE);
>- if (rxq == NULL)
>- return -(ENOMEM);
>- if (nb_queues > old_nb_queues) {
>- uint16_t new_qs = nb_queues -
>old_nb_queues;
>-
>- memset(rxq + old_nb_queues, 0,
>- sizeof(rxq[0]) * new_qs);
>+ rxq[i] = NULL;
> }
>
>- dev->data->rx_queues = rxq;
>-
> } else if (dev->data->rx_queues != NULL && nb_queues == 0) {
> RTE_FUNC_PTR_OR_ERR_RET(*dev->dev_ops-
>>rx_queue_release, -ENOTSUP);
>
>@@ -1138,8 +1129,9 @@ eth_dev_tx_queue_config(struct
>rte_eth_dev *dev, uint16_t nb_queues)
>
> if (dev->data->tx_queues == NULL && nb_queues != 0) { /*
>first time configuration */
> dev->data->tx_queues = rte_zmalloc("ethdev-
>>tx_queues",
>- sizeof(dev->data-
>>tx_queues[0]) * nb_queues,
>-
>RTE_CACHE_LINE_SIZE);
>+ sizeof(dev->data->tx_queues[0]) *
>+ RTE_MAX_QUEUES_PER_PORT,
>+ RTE_CACHE_LINE_SIZE);
> if (dev->data->tx_queues == NULL) {
> dev->data->nb_tx_queues = 0;
> return -(ENOMEM);
>@@ -1149,21 +1141,11 @@ eth_dev_tx_queue_config(struct
>rte_eth_dev *dev, uint16_t nb_queues)
>
> txq = dev->data->tx_queues;
>
>- for (i = nb_queues; i < old_nb_queues; i++)
>+ for (i = nb_queues; i < old_nb_queues; i++) {
> (*dev->dev_ops->tx_queue_release)(txq[i]);
>- txq = rte_realloc(txq, sizeof(txq[0]) * nb_queues,
>- RTE_CACHE_LINE_SIZE);
>- if (txq == NULL)
>- return -ENOMEM;
>- if (nb_queues > old_nb_queues) {
>- uint16_t new_qs = nb_queues -
>old_nb_queues;
>-
>- memset(txq + old_nb_queues, 0,
>- sizeof(txq[0]) * new_qs);
>+ txq[i] = NULL;
> }
>
>- dev->data->tx_queues = txq;
>-
> } else if (dev->data->tx_queues != NULL && nb_queues == 0) {
> RTE_FUNC_PTR_OR_ERR_RET(*dev->dev_ops-
>>tx_queue_release, -ENOTSUP);
>
>--
>2.26.3
next reply other threads:[~2021-10-02 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 0:02 Pavan Nikhilesh Bhagavatula [this message]
2021-10-03 21:05 ` Ananyev, Konstantin
-- strict thread matches above, loose matches on Subject: below --
2021-09-22 14:09 [dpdk-dev] [RFC v2 0/5] hide eth dev related structures Konstantin Ananyev
2021-10-01 14:02 ` [dpdk-dev] [PATCH v3 0/7] " Konstantin Ananyev
2021-10-01 14:02 ` [dpdk-dev] [PATCH v3 1/7] ethdev: allocate max space for internal queue array Konstantin Ananyev
2021-10-01 16:48 ` Ferruh Yigit
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=PH0PR18MB4086A7C510E62F487A289A6CDEAC9@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=adwivedi@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=anoobj@marvell.com \
--cc=beilei.xing@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=heinrich.kuhn@corigine.com \
--cc=hemant.agrawal@nxp.com \
--cc=humin29@huawei.com \
--cc=hyonkim@cisco.com \
--cc=irusskikh@marvell.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=jingjing.wu@intel.com \
--cc=john.miller@atomicrules.com \
--cc=johndale@cisco.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=longli@microsoft.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=mczekaj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=oulijun@huawei.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=shepard.siegel@atomicrules.com \
--cc=somnath.kotur@broadcom.com \
--cc=sthemmin@microsoft.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=xiao.w.wang@intel.com \
--cc=xiaoyun.li@intel.com \
--cc=yisen.zhuang@huawei.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).