From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f54.google.com (mail-qg0-f54.google.com [209.85.192.54]) by dpdk.org (Postfix) with ESMTP id 00463594D for ; Wed, 23 Jul 2014 11:03:15 +0200 (CEST) Received: by mail-qg0-f54.google.com with SMTP id z60so1039475qgd.27 for ; Wed, 23 Jul 2014 02:04:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TzPPD+05QHr3g/koI9dpv4gijOG1rLSDb6XpFONwLoQ=; b=EfS1mCPwkvwZ6z7McNSr/xaB0g/lK82W1JNQ+/Th+g/yaNOjpAV839CAYtZYem9bl4 lNWFk7KgFyFp7jXCxy1wNcwYbR8mGAgs3GWtdkVcK4ehMR3fkTlQl2fKrW/ctNLeeYrl 08LDMDyW2i+sKvk3fcQ/y2YH4zODcX8cYunuRcd1wHEI/jGAoyCzzeZvNC/SgqMRq01A jZ05hlFGPhFrQZEFDWYzavlm7xZSB/SSIYH8HHBXjwITEzK4dF+pYQd8uRYTnjiDt/Rp Va3FCk0onkztY2GtRJRO/h52w2o9D/NG74paVRkpMrgFv/06iqXF5NDIGbIGpSo92D2z 61Og== MIME-Version: 1.0 X-Received: by 10.140.97.117 with SMTP id l108mr58747885qge.29.1406106277639; Wed, 23 Jul 2014 02:04:37 -0700 (PDT) Received: by 10.140.80.34 with HTTP; Wed, 23 Jul 2014 02:04:37 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Jul 2014 13:34:37 +0430 Message-ID: From: Mahdi Dashtbozorgi To: dev@dpdk.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2014 09:03:16 -0000 Hi guys, Is there any suggestion to free the previously allocated memzone? I really need help in this issue. Any help is appreciated. Best Regards, Mahdi. On Tue, Jul 22, 2014 at 4:03 PM, Mahdi Dashtbozorgi wrote: > 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. >