From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mdasht@gmail.com>
Received: from mail-qg0-f54.google.com (mail-qg0-f54.google.com
 [209.85.192.54]) by dpdk.org (Postfix) with ESMTP id 59BCAB365
 for <dev@dpdk.org>; Tue, 22 Jul 2014 13:32:36 +0200 (CEST)
Received: by mail-qg0-f54.google.com with SMTP id z60so6677118qgd.41
 for <dev@dpdk.org>; Tue, 22 Jul 2014 04:33:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=+CyZGES3VpkbxLS3C6TYfQOLPm7qcpjPsfrB9BO8J0A=;
 b=PbkORs4ovqp3qk0DjjLM9ogAgIKKLOy+LRF6neb83/rH165T0VuZ8K5DVI03M3qrdT
 6+YhGUYMNkU2Vt6ZNp6vT7Btq2ud6ekOXEW4JkPNBjgNoQmlaGdLxukKuZPvnxnYU77T
 Tg4iWxjormGArodYTf5nrzOj1TzwN2IJHCMW3tmbzbzdzoFf7iNdgMbd9WgIPPPPplWX
 6ZUcmVqAWbxuHGcWer9+FEcTPd2nOlrquETUDW24fr1SWm1DXcrDsoNef/PU1WZ5UEin
 j9yd8w4u0r9gtgEb9vW8wjpOWnFvkqEvfLY4fkqJLzPCQth9Rh/9LpRh/gZKDNX7L1iW
 dXTg==
MIME-Version: 1.0
X-Received: by 10.140.41.133 with SMTP id z5mr40775139qgz.99.1406028834243;
 Tue, 22 Jul 2014 04:33:54 -0700 (PDT)
Received: by 10.140.80.34 with HTTP; Tue, 22 Jul 2014 04:33:54 -0700 (PDT)
Date: Tue, 22 Jul 2014 16:03:54 +0430
Message-ID: <CAB5=vGbhXPW3YGH+an2PTHW3bBZ-qA_e-pO248qJ3qkb3prm5A@mail.gmail.com>
From: Mahdi Dashtbozorgi <mdasht@gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] free a memzone
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Tue, 22 Jul 2014 11:32:36 -0000

Hi,

I have two processes, which uses DPDK multi-process feature to communicate.
Master process captures packets from NIC and put them to a ring buffer,
which is shared between master and slave process.
The slave process looks up the shared ring buffer using rte_ring_lookup
function and reads the packets.
The slave process needs a memory pool, too. Therefore, it creates a mempool
using rte_mempool_create. But If the slave process crashes during its
processing and runs again, rte_mempool_create function fails and tells that
there is a memory zone with that name.
If I use rte_mempool_lookup in this case, the memory pool is not a clean
memory pool. Because the previous run of slave process did not terminate
gracefully and did not return all the objects to the pool.
Is there any function to free an existing memory zone, which I call before
rte_mempool_create to ensure that previous memory pool does not exists
anymore?

Best Regards,
Mahdi.