DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Karthikraj palanichamy <karthikraj.palanichamy@veryxtech.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Problem in configuring buffer size of a memory pool
Date: Thu, 9 Feb 2017 09:19:07 +0000	[thread overview]
Message-ID: <20170209091906.GA324600@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <589C0E7E.7080400@veryxtech.com>

On Thu, Feb 09, 2017 at 12:08:54PM +0530, Karthikraj palanichamy wrote:
> Hi developers,
> 
> For /`rte_pktmbuf_pool_create()`, /I normally provide
> RTE_MBUF_DEFAULT_BUF_SIZE as the data room size.
> 
> I needed to change this dynamically 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.
> 
> Then I will do `rte_mempool_free()` and create mem pool again whenever
> needed.
> 
> So, my code flow is /create mempool -> transmit pkts -> free mempool/
> 
> When I do 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.
> 
> Thanks in advance for your help.
> 
I think you'll need to stop the transmit ports and possibly destroy and 
recreate the TX queues too. What may be happening is that packet buffers
are remaining on the TX ring after transmit, and then when being freed
to make room for new packet buffers to be transmitted, the mempool to
which they are to be freed no longer exists.

> 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.
> 

Since this is a public mailing list, please remove this disclaimer as
the email cannot be private.

/Bruce

  reply	other threads:[~2017-02-09  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  6:38 Karthikraj palanichamy
2017-02-09  9:19 ` Bruce Richardson [this message]
2017-02-09 10:11   ` Karthikraj palanichamy

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=20170209091906.GA324600@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=karthikraj.palanichamy@veryxtech.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).