From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by dpdk.org (Postfix) with ESMTP id CBBC47E7C for ; Thu, 18 Dec 2014 14:25:40 +0100 (CET) Received: by mail-lb0-f172.google.com with SMTP id u10so959136lbd.17 for ; Thu, 18 Dec 2014 05:25:40 -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=nLMCcrrRiY8gcGHsXz/bs3Te9U4A1j16DuZTWt4Pqcw=; b=j/KpLodkkgjq1d9HtNyhfMclCM+xi78Mr6i7Rw9Se63axnUUIRku2tyRr7RC8n9lRy ascsQk2ohJsrHIc8bnsXzuKpjXC6/TUxicIyonEk3fpSI1kgJKw6pAA4yYNjq66Q5AKo 3vgfOkwnogXpJsVhCDa8sDSk17J4Q1SJQh/V/2D1ToRpUbweaT9z5MJCaavwrmw+K3Pv e/MPGx+alVJckT+a0Sw4DoGvvTWstFEDX0XMCrkbeD57c9HCJ5+N9GWUN5lRJFMOMedj kFoLneYg0zR9W6CMa9aDhVf5N0Dws9iidP8H6I61R0KJRYUAAUsRScIki+Qo2Y9QjuV8 zJtQ== MIME-Version: 1.0 X-Received: by 10.153.11.170 with SMTP id ej10mr2309758lad.24.1418909140362; Thu, 18 Dec 2014 05:25:40 -0800 (PST) Received: by 10.25.216.133 with HTTP; Thu, 18 Dec 2014 05:25:40 -0800 (PST) Date: Thu, 18 Dec 2014 14:25:40 +0100 Message-ID: From: Newman Poborsky To: "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] rte_mempool_create fails with ENOMEM 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, 18 Dec 2014 13:25:41 -0000 Hi, could someone please provide any explanation why sometimes mempool creation fails with ENOMEM? I run my test app several times without any problems and then I start getting ENOMEM error when creating mempool that are used for packets. I try to delete everything from /mnt/huge, I increase the number of huge pages, remount /mnt/huge but nothing helps. There is more than enough memory on server. I tried to debug rte_mempool_create() call and it seems that after server is restarted free mem segments are bigger than 2MB, but after running test app for several times, it seems that all free mem segments have a size of 2MB, and since I am requesting 8MB for my packet mempool, this fails. I'm not really sure that this conclusion is correct. Does anybody have any idea what to check and how running my test app several times affects hugepages? For me, this doesn't make any since because after test app exits, resources should be freed, right? This has been driving me crazy for days now. I tried reading a bit more theory about hugepages, but didn't find out anything that could help me. Maybe it's something else and completely trivial, but I can't figure it out, so any help is appreciated. Thank you! BR, Newman P.