From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) by dpdk.org (Postfix) with ESMTP id 284403195 for ; Tue, 12 Jan 2016 14:57:22 +0100 (CET) Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244]) by mailout1.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O0U002OPERK9010@mailout1.w1.samsung.com> for dev@dpdk.org; Tue, 12 Jan 2016 13:57:20 +0000 (GMT) X-AuditID: cbfec7f4-f79026d00000418a-78-569506400023 Received: from eusync2.samsung.com ( [203.254.199.212]) by eucpsbgm1.samsung.com (EUCPMTA) with SMTP id 71.2E.16778.04605965; Tue, 12 Jan 2016 13:57:20 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O0U00MBBERJUN30@eusync2.samsung.com>; Tue, 12 Jan 2016 13:57:20 +0000 (GMT) From: Pavel Fedin To: 'Sergio Gonzalez Monroy' References: <1446748276-132087-1-git-send-email-jianfeng.tan@intel.com> <1452426182-86851-1-git-send-email-jianfeng.tan@intel.com> <1452426182-86851-3-git-send-email-jianfeng.tan@intel.com> <5694C36D.2040006@intel.com> <00d501d14d20$930c8ae0$b925a0a0$@samsung.com> <5694D9E9.6060704@intel.com> <00de01d14d28$7c2eaf80$748c0e80$@samsung.com> <5694DE7C.4050206@intel.com> <00e301d14d2d$ad9cb350$08d619f0$@samsung.com> <5694EDA4.9030202@intel.com> In-reply-to: <5694EDA4.9030202@intel.com> Date: Tue, 12 Jan 2016 16:57:19 +0300 Message-id: <00ed01d14d41$278cd8d0$76a68a70$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQLOfZuJ4skKn5NxqR5aD7duH+7e0wGBr/PNAXdZpgsCZb31fwF86PJgAWMsQY0CZHOBwQJHg9NpAreV4wACBFfo6AEHbZHSnGgUYOA= Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42I5/e/4FV0HtqlhBu9+iFrMffmDyeLdp+1M Ft2zv7BZ/P/1itXi0KHDjBab3k1itVgx4QijA7vHg8s3mTx+LVjK6tFy5C2rx+I9L5k8ml88 Z/F4v+8qWwBbFJdNSmpOZllqkb5dAlfG00mz2Qq+s1Y8m9LK3sD4lKWLkZNDQsBE4tWCCawQ tpjEhXvr2boYuTiEBJYyStze8QjK+c4osXJ7KztIFZuAusTprx/AukUE7CXOvJ3KCFLELHCJ UaL10B+ojj4Wiec/b4NVcQpoSqzu38wIYgsLhErMWnQCbB+LgKrEomdTgWo4OHgFLCUmbK8H CfMKCEr8mHwPrJVZQEti/c7jTBC2vMTmNW+ZIU5VkNhx9jUjSKuIQIXErNmmECUiEtP+3WOe wCg0C8mkWUgmzUIyaRaSlgWMLKsYRVNLkwuKk9JzDfWKE3OLS/PS9ZLzczcxQmLnyw7Gxces DjEKcDAq8fBmsE8JE2JNLCuuzD3EKMHBrCTCe/k3UIg3JbGyKrUoP76oNCe1+BCjNAeLkjjv 3F3vQ4QE0hNLUrNTUwtSi2CyTBycUg2M8rVmc90UbN7I2ljF/K2x9Wu8d5dNco3559dB3z4r /pnHN0/nCUuOos11zVi7D9OCds/sDwi/Eudut3VhqJu3u3Ni4q3DEr9Kj7U6nNF/l5vkWmXN NGOFYM+8edfSeuo2ODzovCTctjFw+hHNGRbbLPN9ry15fv/dieCJ6yxSP6kkMs7w7MtWYinO SDTUYi4qTgQAlqlJHpkCAAA= Cc: nakajima.yoshihiro@lab.ntt.co.jp, "'Michael S. Tsirkin'" , dev@dpdk.org, ann.zhuangyanying@huawei.com Subject: Re: [dpdk-dev] [PATCH 2/4] mem: add API to obstain memory-backed file info 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: Tue, 12 Jan 2016 13:57:22 -0000 Hello! > I might be missing something obvious here but, aside from having memory > SHARED which most DPDK apps using hugepages will have anyway, what is > the backward compatibility issues that you see here? Heh, sorry once again for confusing. Indeed, with hugepages we always get MAP_SHARED. I missed that. So, we indeed need --shared-mem only in addition to --no-huge. Backwards compatibility issue is stated in the description of PATCH 1/4: --- cut --- b. possible ABI break, originally, --no-huge uses anonymous memory instead of file-backed way to create memory. --- cut --- The patch unconditionally changes that to SHARED. That's all. Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia