From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id DAF368D9B for ; Thu, 15 Oct 2015 14:33:00 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 15 Oct 2015 05:33:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,685,1437462000"; d="scan'208";a="827333408" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by orsmga002.jf.intel.com with ESMTP; 15 Oct 2015 05:32:58 -0700 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.139]) by irsmsx110.ger.corp.intel.com ([169.254.15.151]) with mapi id 14.03.0248.002; Thu, 15 Oct 2015 13:32:57 +0100 From: "Burakov, Anatoly" To: Nissim Nisimov , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] eal:Map rte cfg and uio at the end of hugepage mem Thread-Index: AQHRB0NsvfYun4erIUKWwC9OuLyJR55sfGAg Date: Thu, 15 Oct 2015 12:32:57 +0000 Message-ID: References: <1444911367-23738-1-git-send-email-nissimn@radware.com> In-Reply-To: <1444911367-23738-1-git-send-email-nissimn@radware.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] eal:Map rte cfg and uio at the end of hugepage mem 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, 15 Oct 2015 12:33:02 -0000 Hi > Problem: > In DPDK Primary/Secondary module we assume mapping same regions of > virtual memory addresses for Primary process and Secondary. > An issue may occur when the Primary and secondary processes are not > symmetric in such way that the code is not the same (for example, Primary > process is a traffic distributer and secondary is a worker). The result m= ay be > that specific virtual address region in the first process won't be availa= ble in > the second process. >=20 > Changes done at eal init: > map all related rte configuration and uio sections close to the end of hu= ge > pages memory (that mean rte_eal_memory_init() should be called before > rte_config_init() in primary process) > According to our observations there will be more probability to success w= hen > allocating rte_config and uio memzones after huge pages sections (actuall= y > uio is already allocated after the huge pages area) Not sure I understand the purpose of the patch. Doesn't --base-virtaddr fla= g solve your issues? Thanks, Anatoly