From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout1.radware.com (unknown [192.115.180.130]) by dpdk.org (Postfix) with ESMTP id 255E38E93 for ; Mon, 23 Nov 2015 16:33:19 +0100 (CET) Received: from ILMB1.corp.radware.com ([169.254.1.202]) by ILCAS1.corp.radware.com ([176.200.120.121]) with mapi id 14.03.0210.002; Mon, 23 Nov 2015 17:33:12 +0200 From: Nissim Nisimov To: "dev@dpdk.org" Thread-Topic: max MEMZONEs allowed Thread-Index: AdEmA+sB1Pf4HyXYTIa0B+7b9t4KbQ== Date: Mon, 23 Nov 2015 15:33:11 +0000 Message-ID: <94AA676E9B9A384A844E7692F3CAD906C5548CD7@ILMB1.corp.radware.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [176.200.120.205] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2015 15:33:19 -0000 Hi all, We are working on a system which requires allocating a big number of mem zo= nes. We are now reaching the max limit of MEMZONEs allowed (RTE_MAX_MEMZONE).=20 I see today dpdk limit the above number to 2560.=20 Is there any specific reason for that? can I increase it in case needed. Wh= at may be the side effects of such changes? Thx Nissim