From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dror Birkman <dror.birkman@lightcyber.com>
Subject: PCAP memory leak in freeing jumbo frames
Date: Thu, 3 Nov 2016 11:35:14 +0200
Message-ID: <CAMLkaUvupSKK0=5RHPVikVSXgHEioehRpSYpLLcSobOgR+USkA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: Nicolas Pernas Maradei <nicolas.pernas.maradei@emutex.com>,
 ferruh.yigit@intel.com
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mail-qt0-f177.google.com (mail-qt0-f177.google.com
 [209.85.216.177]) by dpdk.org (Postfix) with ESMTP id 1092329CA
 for <dev@dpdk.org>; Thu,  3 Nov 2016 10:35:15 +0100 (CET)
Received: by mail-qt0-f177.google.com with SMTP id c47so24407407qtc.2
 for <dev@dpdk.org>; Thu, 03 Nov 2016 02:35:15 -0700 (PDT)
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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