DPDK usage discussions
 help / color / mirror / Atom feed
From: Karthikraj palanichamy <karthikraj.palanichamy@veryxtech.com>
To: users@dpdk.org
Subject: [dpdk-users] Issue in freeing and recreating mempools for Transmission
Date: Fri, 17 Feb 2017 15:44:14 +0530	[thread overview]
Message-ID: <58A6CCF6.9070804@veryxtech.com> (raw)

Hi!

I am using dpdk to develop a traffic generator (both rx and tx).

At the start, I will create a memory pool for Rx with default data room 
size : RTE_MBUF_DEFAULT_BUF_SIZE.

For Tx, I will dynamically create memory pool based on the frame size to 
be transmitted.

To transmit 80 bytes frames, I configured (80 +/RTE_PKTMBUF_HEADROOM/). 
There was no problem and transmission was successful.

I will do `rte_mempool_free()` once the transmission is over.

I will again create mem pool when transmission is again set ON.

So, my code flow is /: create mempool -> transmit pkts -> free mempool/

When I repeat this for 3 to 5 times, I get segmentation fault in the 
transmission API of the PMD. - 'eth_igb_xmit_pkts' for igb PMD and  
'ixgbe_xmit_pkts_vec()' for ixgbe PMD.

When I do /`rte_eth_dev_close()`/ and `rte_eth_dev_start()` after 
freeing the mem pool, everything works fine.

But I couldn't afford to do `rte_eth_dev_close()` since Rx will be 
running in parallel and Rx shouldn't be stopped.

I tried `rte_eth_dev_tx_queue_stop()` but issue persists.

Thanks in advance for any help.

Regards
Karthik

DISCLAIMER: Privileged and/or Confidential information may be
contained in this message. If you are not the addressee of this message,
you may not copy, use or deliver this message to anyone. In such
event,you should destroy the message and kindly notify the sender by
reply e-mail.
It is understood that opinions or conclusions that do not relate to the
official business of the company are neither given nor endorsed by the
company.

                 reply	other threads:[~2017-02-17 10:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=58A6CCF6.9070804@veryxtech.com \
    --to=karthikraj.palanichamy@veryxtech.com \
    --cc=users@dpdk.org \
    /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).