DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dror Birkman <dror.birkman@lightcyber.com>
To: dev@dpdk.org
Cc: Nicolas Pernas Maradei <nicolas.pernas.maradei@emutex.com>,
	ferruh.yigit@intel.com
Subject: [dpdk-dev] PCAP memory leak in freeing jumbo frames
Date: Thu, 3 Nov 2016 11:35:14 +0200	[thread overview]
Message-ID: <CAMLkaUvupSKK0=5RHPVikVSXgHEioehRpSYpLLcSobOgR+USkA@mail.gmail.com> (raw)

Hi,

I have a huge memory leak when I release mbufs allocated
by eth_pcap_rx_jumbo().

I use rte_mempool_put_bulk() to release the mbufs.
To my horror I found out it puts back to the mempool only the head mbuf and
not its segments!

I know rte_pktmbuf_free() frees the mbuf and all it segments, but afaik it
is not thread safe.

What is the thread safe way to free mbufs (preferably in bulk) and their
segments?

TIA,
Dror

             reply	other threads:[~2016-11-03  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03  9:35 Dror Birkman [this message]
2016-11-03 10:23 ` Bruce Richardson

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='CAMLkaUvupSKK0=5RHPVikVSXgHEioehRpSYpLLcSobOgR+USkA@mail.gmail.com' \
    --to=dror.birkman@lightcyber.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nicolas.pernas.maradei@emutex.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).