From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vb0-x230.google.com (mail-vb0-x230.google.com [IPv6:2607:f8b0:400c:c02::230]) by dpdk.org (Postfix) with ESMTP id 4D79F18F for ; Thu, 19 Dec 2013 11:56:54 +0100 (CET) Received: by mail-vb0-f48.google.com with SMTP id f13so528780vbg.21 for ; Thu, 19 Dec 2013 02:58:00 -0800 (PST) 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=K826HAolXQTD4uDU/g4pCi03q8fVKHzzE6S8+OmBy/4=; b=UtarMf8l0ELuWxXPZ8PIgMuEy6MKuvPAZSlJNGaMCP0fUKT/9Np9e/hauhDTquMnoG Otc2+P0zMKeew6zzmqlLh9RGtidhnKtMrqhGoaDEK64dbWPi7EGzkClZckPYeKs//Xz5 1Fl+iKOqzsLTfv0WQOoTPmZEWOfVTCzf10RBub4uQ7zjNr+xkztCIZjjitZMcQmGlYQy NSyiJm7q3VU5o61pulIXmYwVllRqBgEjcltWgnIuCuIjNx0FeggFL4jVurCsP5xuJb2s 4lu2Vj9aDl115D6sYfdwPiXbHdvhjk8J0rFpatu5rPRuIUge2WMzAHDjliRk8ydfdPi0 ySZA== MIME-Version: 1.0 X-Received: by 10.220.159.4 with SMTP id h4mr403370vcx.1.1387450679816; Thu, 19 Dec 2013 02:57:59 -0800 (PST) Received: by 10.52.113.228 with HTTP; Thu, 19 Dec 2013 02:57:59 -0800 (PST) Date: Thu, 19 Dec 2013 16:27:59 +0530 Message-ID: From: ankit kumar To: dev Content-Type: text/plain; charset=ISO-8859-1 Subject: [dpdk-dev] Is rte_mempool library is multi-thread safe ??? 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: Thu, 19 Dec 2013 10:56:54 -0000 Hi, I was testing rte_ring in DPDK as it provides multi-consumer & multi-produce queue(lock-free but not wait-free). It was working fine but i am not sure that memory allocation & deallocation in rte_mempool library, is multi-thread safe or not. Because its giving me error during allocation(from multi-thread) as "Allocation failed(returned pointer is NULL in allocation function rte_pktmbuf_alloc())" & during rte_pktmbuf_free() it generates segmentation fault and when i traced out, core file generated, it indicated that the problem is in rte_pktmbuf_free(). Any help !!!