From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sergio.gonzalez.monroy@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 70BDB591E
 for <dev@dpdk.org>; Tue, 24 Nov 2015 09:44:10 +0100 (CET)
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by orsmga101.jf.intel.com with ESMTP; 24 Nov 2015 00:44:09 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,338,1444719600"; 
   d="scan'208";a="1437174"
Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.220.55])
 ([10.237.220.55])
 by fmsmga004.fm.intel.com with ESMTP; 24 Nov 2015 00:44:08 -0800
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Nissim Nisimov <nissimn@radware.com>
References: <94AA676E9B9A384A844E7692F3CAD906C5548CD7@ILMB1.corp.radware.com>
Message-ID: <56542357.4090901@intel.com>
Date: Tue, 24 Nov 2015 08:44:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <94AA676E9B9A384A844E7692F3CAD906C5548CD7@ILMB1.corp.radware.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] max MEMZONEs allowed
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2015 08:44:10 -0000

On 23/11/2015 15:33, Nissim Nisimov wrote:
> Hi all,
>
> We are working on a system which requires allocating a big number of mem zones.
>
> We are now reaching the max limit of MEMZONEs allowed (RTE_MAX_MEMZONE).
>
> I see today dpdk limit the above number to 2560.
> Is there any specific reason for that? can I increase it in case needed. What may be the side effects of such changes?
>
You can increase the number of memsegs, 256 is just a default value.
The only side-effect I can think of, on systems that use more than the 
default number of memsegs, is slower EAL initialization and increased 
memseg lookup time.

Sergio
> Thx
> Nissim