From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Fedin Subject: Re: [PATCH 2/4] mem: add API to obstain memory-backed file info Date: Tue, 12 Jan 2016 15:01:30 +0300 Message-ID: <00e601d14d30$f9ebbc80$edc33580$@samsung.com> 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> <00e201d14d2b$77e03590$67a0a0b0$@samsung.com> <5694E46F.20508@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: nakajima.yoshihiro@lab.ntt.co.jp, "'Michael S. Tsirkin'" , dev@dpdk.org, ann.zhuangyanying@huawei.com To: 'Sergio Gonzalez Monroy' Return-path: Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com [210.118.77.13]) by dpdk.org (Postfix) with ESMTP id 214308DAF for ; Tue, 12 Jan 2016 13:01:33 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O0U009NS9EKDZA0@mailout3.w1.samsung.com> for dev@dpdk.org; Tue, 12 Jan 2016 12:01:32 +0000 (GMT) In-reply-to: <5694E46F.20508@intel.com> Content-language: ru List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello! > > .repeated depends on CONFIG_RTE_EAL_SIGLE_FILE_SEGMENTS. By the = way, looks like it does > the same thing as you are trying to do with --single-file, but with = hugepages, doesn't it? I > see it's currently used by ivshmem (which is AFAIK very immature and = half-abandoned). >=20 > Similar but not the same. > --single-file: a single file for all mapped hugepages. > SINGLE_FILE_SEGMENTS: a file per set of physically contiguous mapped > hugepages (what DPDK calls memseg , memory segment). So there could be > more than one file. Thank you for the explanation. By this time, i've done more testing. Current patchset breaks = --no-huge. I did not study why: --- cut --- Program received signal SIGBUS, Bus error. malloc_elem_init (elem=3Delem@entry=3D0x7fffe51e6000, = heap=3D0x7ffff7fe5a1c, ms=3Dms@entry=3D0x7ffff7fb301c, = size=3Dsize@entry=3D268435392) at = /home/p.fedin/dpdk/lib/librte_eal/common/malloc_elem.c:62 62 /home/p.fedin/dpdk/lib/librte_eal/common/malloc_elem.c: No such file = or directory. Missing separate debuginfos, use: dnf debuginfo-install = keyutils-libs-1.5.9-7.fc23.x86_64 krb5-libs-1.13.2-11.fc23.x86_64 = libcap-ng-0.7.7-2.fc23.x86_64 libcom_err-1.42.13-3.fc23.x86_64 = libselinux-2.4-4.fc23.x86_64 openssl-libs-1.0.2d-2.fc23.x86_64 = pcre-8.37-4.fc23.x86_64 zlib-1.2.8-9.fc23.x86_64 (gdb) where #0 malloc_elem_init (elem=3Delem@entry=3D0x7fffe51e6000, = heap=3D0x7ffff7fe5a1c, ms=3Dms@entry=3D0x7ffff7fb301c, = size=3Dsize@entry=3D268435392) at /home/p.fedin/dpdk/lib/librte_eal/common/malloc_elem.c:62 #1 0x00000000004a50b5 in malloc_heap_add_memseg (ms=3D0x7ffff7fb301c, = heap=3D) at = /home/p.fedin/dpdk/lib/librte_eal/common/malloc_heap.c:109 #2 rte_eal_malloc_heap_init () at = /home/p.fedin/dpdk/lib/librte_eal/common/malloc_heap.c:232 #3 0x00000000004be896 in rte_eal_memzone_init () at = /home/p.fedin/dpdk/lib/librte_eal/common/eal_common_memzone.c:427 #4 0x000000000042ab02 in rte_eal_init (argc=3Dargc@entry=3D11, = argv=3Dargv@entry=3D0x7fffffffeb80) at = /home/p.fedin/dpdk/lib/librte_eal/linuxapp/eal/eal.c:799 #5 0x000000000066dfb9 in dpdk_init (argc=3D11, argv=3D0x7fffffffeb80) = at lib/netdev-dpdk.c:2192 #6 0x000000000040ddd9 in main (argc=3D12, argv=3D0x7fffffffeb78) at = vswitchd/ovs-vswitchd.c:74 --- cut --- And now i tend to think that we do not need --single-file at all. = Because: a) It's just a temporary workaround for "more than 8 regions" problem. b) It's not compatible with physical hardware anyway. So i think that we could easily use "--no-huge --shared-mem" = combination. We could address hugepages compatibility problem later. Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia