From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jeff Guo <jia.guo@intel.com>,
Renata Saiakhova <Renata.Saiakhova@ekinops.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/4] librte_ethdev: Introduce a function to release HW rings
Date: Fri, 19 Jun 2020 18:06:06 +0100 [thread overview]
Message-ID: <4767a7e4-80d6-1c23-8bba-3a0bce2266fd@intel.com> (raw)
In-Reply-To: <5aa2d634-f896-3204-f557-38f7bacfe513@intel.com>
On 5/15/2020 9:04 AM, Jeff Guo wrote:
> hi, renata
>
> On 5/13/2020 9:14 PM, Renata Saiakhova wrote:
>> Free previously allocated memzone for HW rings
>>
>> Signed-off-by: Renata Saiakhova <Renata.Saiakhova@ekinops.com>
>> ---
>> lib/librte_ethdev/rte_ethdev.c | 28 ++++++++++++++++++++++--
>> lib/librte_ethdev/rte_ethdev_driver.h | 20 +++++++++++++++++
>> lib/librte_ethdev/rte_ethdev_version.map | 1 +
>> 3 files changed, 47 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/librte_ethdev/rte_ethdev.c b/lib/librte_ethdev/rte_ethdev.c
>> index 72aed59a5..55f047e22 100644
>> --- a/lib/librte_ethdev/rte_ethdev.c
>> +++ b/lib/librte_ethdev/rte_ethdev.c
>> @@ -4181,6 +4181,10 @@ rte_eth_dev_rx_intr_ctl_q_get_fd(uint16_t port_id, uint16_t queue_id)
>> return fd;
>> }
>>
>> +#define ETH_DMA_MZONE_NAME(_name, _port_id, _queue_id, _ring_name) \
>> + snprintf(_name, sizeof(_name), "eth_p%d_q%d_%s", \
>> + _port_id, _queue_id, _ring_name)
>> +
>> const struct rte_memzone *
>> rte_eth_dma_zone_reserve(const struct rte_eth_dev *dev, const char *ring_name,
>> uint16_t queue_id, size_t size, unsigned align,
>> @@ -4190,8 +4194,7 @@ rte_eth_dma_zone_reserve(const struct rte_eth_dev *dev, const char *ring_name,
>> const struct rte_memzone *mz;
>> int rc;
>>
>> - rc = snprintf(z_name, sizeof(z_name), "eth_p%d_q%d_%s",
>> - dev->data->port_id, queue_id, ring_name);
>> + rc = ETH_DMA_MZONE_NAME(z_name, dev->data->port_id, queue_id, ring_name);
>> if (rc >= RTE_MEMZONE_NAMESIZE) {
>> RTE_ETHDEV_LOG(ERR, "ring name too long\n");
>> rte_errno = ENAMETOOLONG;
>> @@ -4206,6 +4209,27 @@ rte_eth_dma_zone_reserve(const struct rte_eth_dev *dev, const char *ring_name,
>> RTE_MEMZONE_IOVA_CONTIG, align);
>> }
>>
>> +int
>> +rte_eth_dma_zone_free(const struct rte_eth_dev *dev, const char *ring_name,
>> + uint16_t queue_id)
>> +{
>> + char z_name[RTE_MEMZONE_NAMESIZE];
>> + const struct rte_memzone *mz;
>> + int rc = 0;
>> +
>> + rc = ETH_DMA_MZONE_NAME(z_name, dev->data->port_id, queue_id, ring_name);
>> + if (rc >= RTE_MEMZONE_NAMESIZE) {
>> + RTE_ETHDEV_LOG(ERR, "ring name too long\n");
>> + return -ENAMETOOLONG;
>> + }
>> +
>> + mz = rte_memzone_lookup(z_name);
>> + if (mz)
>> + rc = rte_memzone_free(mz);
>> +
>> + return rc;
>
>
> If rc < RTE_MEMZONE_NAMESIZE && !mz, what value should be return base
> on the parameter description in .h?
+1,
When 'mz' not found return value will be wrong according API documentation.
>
> Although it would not affect the other patch set, but could you please
> clarify it?
>
>
>> +}
>> +
>> int
>> rte_eth_dev_create(struct rte_device *device, const char *name,
>> size_t priv_data_size,
>> diff --git a/lib/librte_ethdev/rte_ethdev_driver.h b/lib/librte_ethdev/rte_ethdev_driver.h
>> index 99d4cd6cd..462e765d1 100644
>> --- a/lib/librte_ethdev/rte_ethdev_driver.h
>> +++ b/lib/librte_ethdev/rte_ethdev_driver.h
>> @@ -180,6 +180,26 @@ rte_eth_dma_zone_reserve(const struct rte_eth_dev *eth_dev, const char *name,
>> uint16_t queue_id, size_t size,
>> unsigned align, int socket_id);
>>
>> +/**
>> + * @warning
>> + * @b EXPERIMENTAL: this API may change without prior notice.
>> + *
>> + * Free previously allocated memzone for HW rings.
>> + *
>> + * @param eth_dev
>> + * The *eth_dev* pointer is the address of the *rte_eth_dev* structure
>> + * @param name
>> + * The name of the memory zone
>> + * @param queue_id
>> + * The index of the queue to add to name
>> + * @return
>> + * Negative errno value on error, 0 on success.
>> + */
>> +__rte_experimental
>> +int
>> +rte_eth_dma_zone_free(const struct rte_eth_dev *dev, const char *ring_name,
>> + uint16_t queue_id);
>> +
>> /**
>> * @internal
>> * Atomically set the link status for the specific device.
>> diff --git a/lib/librte_ethdev/rte_ethdev_version.map b/lib/librte_ethdev/rte_ethdev_version.map
>> index 715505604..139a81302 100644
>> --- a/lib/librte_ethdev/rte_ethdev_version.map
>> +++ b/lib/librte_ethdev/rte_ethdev_version.map
>> @@ -241,4 +241,5 @@ EXPERIMENTAL {
>> __rte_ethdev_trace_rx_burst;
>> __rte_ethdev_trace_tx_burst;
>> rte_flow_get_aged_flows;
>> + rte_eth_dma_zone_free;
>> };
next prev parent reply other threads:[~2020-06-19 17:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 13:14 [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings allocation Renata Saiakhova
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 1/4] librte_ethdev: Introduce a function to release HW rings Renata Saiakhova
2020-05-14 13:14 ` Burakov, Anatoly
2020-05-15 8:04 ` Jeff Guo
2020-06-19 17:06 ` Ferruh Yigit [this message]
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 2/4] drivers/net: Fix in igb and ixgbe HW rings memory Renata Saiakhova
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 3/4] drivers/net: Fix in i40e HW rings memory overlap Renata Saiakhova
2020-06-01 7:58 ` Zhao1, Wei
2020-06-19 16:56 ` Ferruh Yigit
2020-06-20 3:02 ` Zhao1, Wei
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 4/4] drivers/net: Fix in em and ice " Renata Saiakhova
2020-05-13 15:22 ` [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings allocation Ferruh Yigit
2020-05-18 9:48 ` Renata Saiakhova
2020-06-03 1:36 ` Zhao1, Wei
2020-06-19 16:54 ` Ferruh Yigit
2020-06-19 16:54 ` Ferruh Yigit
2020-06-22 9:59 ` Renata Saiakhova
2020-06-20 3:27 ` Zhao1, Wei
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=4767a7e4-80d6-1c23-8bba-3a0bce2266fd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Renata.Saiakhova@ekinops.com \
--cc=dev@dpdk.org \
--cc=jia.guo@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).