From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id 1A3356895 for ; Wed, 14 May 2014 11:15:28 +0200 (CEST) Received: by mail-wi0-f172.google.com with SMTP id hi2so7640931wib.17 for ; Wed, 14 May 2014 02:15:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=zEu1YMTrs44ahXkOXO0FSlztuA3fWtlKENXMOW4LikA=; b=cCAwAxL3r0WpF61KZZKUqNHH87h60rhDAXpg7jKnYwVYL+lFvZcvl1MkOMdRzFyF4o OOI3k+XBsl7swMFymIhBCMnbG39YAgTmDBzn/k/Zn0ADgmLjVYsx0OKUf7/84hF6Bzqx B3a1+nDF46bjfeaLyjY/s+YiPHjwFZflgcqs/bk7cN0D2AfdG4j36A2Pj+bAABAIAYLB NHbMHB5yuk+Q/eThKsLWevg/HYRN/fkIU0Gd3PFCvnML1wPT4CJ4CVruztYPYQkcHi+S WFCZcs1DsPg9LMqY2D97gIpYQ1m6ntC0vvZfPHEX6KsSnUfkZeqgNlbS0mTYO05iHWy9 PbIA== X-Gm-Message-State: ALoCoQlwQmDesqTCa7MF9nINFMOQK0BPs/B9dJQjw7wli1H3oH6tX6+aFO0MFVn2kNCZZFrsdznW X-Received: by 10.195.12.14 with SMTP id em14mr2023411wjd.15.1400058936508; Wed, 14 May 2014 02:15:36 -0700 (PDT) Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.180.237]) by mx.google.com with ESMTPSA id mw4sm26646426wib.12.2014.05.14.02.15.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 May 2014 02:15:35 -0700 (PDT) From: Thomas Monjalon To: Didier Pallard Date: Wed, 14 May 2014 11:15:34 +0200 Message-ID: <4867043.OXANNGufED@xps13> Organization: 6WIND User-Agent: KMail/4.13 (Linux/3.14.2-1-ARCH; KDE/4.13.0; x86_64; ; ) In-Reply-To: <1FD9B82B8BF2CF418D9A1000154491D9740AADF4@ORSMSX102.amr.corp.intel.com> References: <1399642242-19725-1-git-send-email-david.marchand@6wind.com> <1FD9B82B8BF2CF418D9A1000154491D9740AADF4@ORSMSX102.amr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2] eal: change default per socket memory 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: Wed, 14 May 2014 09:15:29 -0000 > Currently, if there is more memory in hugepages than the amount reque= sted by > dpdk application, the memory is allocated by taking as much memory as= > possible from each socket, starting from first one. For example if a > system is configured with 8 GB in 2 sockets (4 GB per socket), and dp= dk is > requesting only 4GB of memory, all memory will be taken in socket 0 (= that > have exactly 4GB of free hugepages) even if some cores are configured= on > socket 1, and there are free hugepages on socket 1...=20 > Change this behaviour to allocate memory on all sockets where some co= res are > configured, spreading the memory amongst sockets using following rati= o per > socket: > N=B0 of cores configured on the socket / Total number of configured > cores * requested memory >=20 > This algorithm is used when memory amount is specified globally using= -m > option. Per socket memory allocation can always be done using --socke= t-mem > option. =20 > Changes included in v2: > - only update linux implementation as bsd looks not to be ready for n= uma > - if new algorithm fails, then defaults to previous behaviour >=20 > Signed-off-by: Didier Pallard > Signed-off-by: David Marchand >=20 > Acked-by: Venky Venkatesan Applied for version 1.7.0. Thanks --=20 Thomas