From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C309FA329E for ; Wed, 23 Oct 2019 19:46:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 04AB51D157; Wed, 23 Oct 2019 19:46:55 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 0FBF91C2B9 for ; Wed, 23 Oct 2019 19:46:52 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2019 10:46:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,221,1569308400"; d="scan'208";a="281691831" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.252.8.129]) ([10.252.8.129]) by orsmga001.jf.intel.com with ESMTP; 23 Oct 2019 10:46:50 -0700 To: Li Han , thomas@monjalon.net Cc: dev@dpdk.org References: <1571827361-30578-1-git-send-email-han.li1@zte.com.cn> From: "Burakov, Anatoly" Message-ID: Date: Wed, 23 Oct 2019 18:46:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <1571827361-30578-1-git-send-email-han.li1@zte.com.cn> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime config mmap issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 23-Oct-19 11:42 AM, Li Han wrote: > In rte_eal_config_reattach(),the secondary mmap may fail > due to the rte_mem_cfg_addr already be used by others.do > the change just as the rte_fbarray_init() do.if no > base_virtaddr,use the default 0x100000000. > > v2/v3: > -fix code style issues > > Signed-off-by: Li Han > --- Nack. There's a reason why we map it at the same address, and it's to have all pointers working across processes. Remapping it at a different address has potential to break things. -- Thanks, Anatoly