From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f175.google.com (mail-pf0-f175.google.com [209.85.192.175]) by dpdk.org (Postfix) with ESMTP id 56B7F5A41 for ; Wed, 17 Aug 2016 17:39:37 +0200 (CEST) Received: by mail-pf0-f175.google.com with SMTP id p64so38682791pfb.1 for ; Wed, 17 Aug 2016 08:39:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=J2DVLQ4ezSrUNCDvkGrMgCS/xhe7uIsivYhM7w047MA=; b=C1CMVSbEdXQCfJ6en9T4FA07q2Duz7D7C7VXH6YTCyokTVga6dNBLO4tYXfaY79GIB igeJT8FWkRnnuJUMc9raMRMfpU7f9hAW9RE1bmFgnJBRMIrBNFy3mnYoqsWzw5pP2wJn Qb39zdjqK+b9p4JrkoYdunE15LErD0kEorsZTE8xHMOCBRDtIfK8RejeU/126ELoRyFt ciSaBqmZkPBfKNv/Hccy0D26C7tBoJO+htas2jvv99MckVsDDmwf6M6XGr1bg2sC2wNc gOf+SJFBtZH7IF2wBKNIKgvOpXtrXOL5Qm4S5DJt8nyM1QkA+dkNHM22k01rMfyqX7l7 epLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=J2DVLQ4ezSrUNCDvkGrMgCS/xhe7uIsivYhM7w047MA=; b=POH2EISOGi4unwYRPBrvVkfPwKCq+AwiZTpvnszBXSbemQsB++0I/UZButhldxQ8HI geEA2oc5A5Awa5e2ahW0+dj9/zZ94RPW240f4Nl6+ZxQXVTAfWI4Pi+uO2G4ssJRYbDB ivJTJMnOLDxzJSW9wPg5CkbXcKwO495lBexzUGZayZwKP+iiP1ieBJ6uqVz4gyGIsXbd 4boByoJgcHIe3780/81ItN1/kIXDqqHh65At6L9FZN7OcB6WN9nkY1/7hOFvwuY8SnGg AnWAXaTsVrPo/M1fnZAj2IUZ7Qi0RwgCqxNoDrgbWzT0H6dERRjVGCfHJgy2jgnmihcq 7Rew== X-Gm-Message-State: AEkoout/IPjF8kvrL2Nmd+9cKNYztnJXmVZUqmJ5BP/aHoydtF0PTTUBBlxF9AYZLVWccg== X-Received: by 10.98.36.15 with SMTP id r15mr25080719pfj.1.1471448376626; Wed, 17 Aug 2016 08:39:36 -0700 (PDT) Received: from xeon-e3 (static-50-53-69-251.bvtn.or.frontiernet.net. [50.53.69.251]) by smtp.gmail.com with ESMTPSA id g10sm48103723pfc.57.2016.08.17.08.39.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 17 Aug 2016 08:39:36 -0700 (PDT) Date: Wed, 17 Aug 2016 08:39:48 -0700 From: Stephen Hemminger To: Sarthak Ray Cc: "users@dpdk.org" Message-ID: <20160817083948.5024edec@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Mempool allocation fails on first boot; but succeeds after system reboot X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 15:39:37 -0000 On Wed, 17 Aug 2016 13:10:35 +0000 Sarthak Ray wrote: > Hi, > > I am using dpdk-2.1.0 for a platform appliance, where I am facing issue with mempool allocation. > > On the firstboot of the newly installed appliance, my dpdk application is not coming up saying failure in mbuf allocation on socket 0. But once I reboot the system, it comes up without any issues. How big is the huge page memory on the system? On initial boot, the free memory is usually contiguous after a lot of programs run it gets fragmented. You can configure grub command line to reserve huge pages before userspace starts; see kernel documentation Documentation/vm/hugepages.txt