From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f68.google.com (mail-pa0-f68.google.com [209.85.220.68]) by dpdk.org (Postfix) with ESMTP id 3E89E5591 for ; Thu, 25 Aug 2016 14:49:47 +0200 (CEST) Received: by mail-pa0-f68.google.com with SMTP id vy10so3083440pac.0 for ; Thu, 25 Aug 2016 05:49:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=HCznzGOzFL1ipxg95Yk0g0X0scn0uxu+jDYu6lVWtbQ=; b=lkjKCQfbY2FmL8WemRTzmzyDzrNwBWcqiPZzcNXeCooOO0LRd3CTI4lnP+CMSQ8kGx QJBcix4AippNzIwFLlGfKseRT/rB0e80tTe4EQxMj7FQils0AWQYBJOHBtKTccPjCzdI L6baidarseYSBFz7hVYLhw59mHv0k/cGWW+69ZsoovExp1f2iJ8vlPmz3p29b0fF3oYO vPqEr7UX4T/lE7U/1LO0SxId8ZDuBCS1nqUqwuxH6Pz99evN5ElB1R6ts2Ypa2mQ9nWJ 9HPZX4uXHzeMaUYTjvdeCN8qlIwFtQ2I3Ra6LnRGLcHqz5mznhK7ujnEnhBtZg2y2v81 Pqdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=HCznzGOzFL1ipxg95Yk0g0X0scn0uxu+jDYu6lVWtbQ=; b=RXCppTkCPh32HEAdnFNmqXch6mIElIMTItcnWri4KDkVuWfNDUc/zaaMVCSjdO7zmQ OM2BCb6xtHl172TXWk4E8fhcMUGOFQURdW2Z+LlBemANDEbnL/OGyk2tprfxCBBmDBKd kH3kumS3X83Nr1IUj4/8k1YQ+wkvDgOd+UCXIcrUHVJ1dziUF8ixgjbd5t8nDAvWLgCz LbbuNtTkKbwJ9iuPenCWPChr7ZLDHoE8faW7hN/tc8ECODE0urgUIKdoJth6/FXcxP85 unPWcr/W3eA05CijcDf2QljG37LYxYP1PI1L74OnNCY/x4P94ba6gG1mrf9MqbbTUZDw ANmA== X-Gm-Message-State: AE9vXwPhg/30hRn4v8jgsXhuURosGTMD8dsZS0Ftq4NI72xZIkhxGgmFCrLf+hkii8BEgw== X-Received: by 10.66.132.38 with SMTP id or6mr15800493pab.84.1472129386516; Thu, 25 Aug 2016 05:49:46 -0700 (PDT) Received: from localhost ([14.141.235.254]) by smtp.gmail.com with ESMTPSA id ty6sm20908651pac.18.2016.08.25.05.49.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 25 Aug 2016 05:49:45 -0700 (PDT) References: <9114674.mxuR5Pefat@polaris> <3F3704B6-4858-4967-960F-E5284F1B17CF@intel.com> User-agent: mu4e 0.9.16; emacs 24.5.1 From: anupam To: Gregory Etelson Cc: "Wiles\, Keith" , "dev\@dpdk.org" In-reply-to: <3F3704B6-4858-4967-960F-E5284F1B17CF@intel.com> Date: Thu, 25 Aug 2016 18:19:42 +0530 Message-ID: <8737lt813t.fsf@fatcat.parallelwireless> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [dpdk-dev] Huge ring allocation 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, 25 Aug 2016 12:49:47 -0000 >>>>> [2016-08-25T17:52:26+0530]: "Keith Wiles" (keith-wiles): ,----[ keith-wiles ] | Another issue sometimes is huge pages are allocated after the system | has booted, which means you need to assign the number of huge pages very | early in the boot process. This means adding a line in the sysctrl.conf | file instead of poking the value later. | | vm.nr_hugepages=XXX `---- you might also try passing 'hugepages' option as kernel command line parameters e.g. '... hugepages=N ' from linux-kernel's Documentation/vm/hugetlbpage.txt we have the following ,----[Documentation/vm/hugetlbpage.txt:69] | The administrator can allocate persistent huge pages on the kernel boot | command line by specifying the "hugepages=N" parameter, where 'N' = the | number of huge pages requested. This is the most reliable method of | allocating huge pages as memory has not yet become fragmented. `---- --- thanks anupam