From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout4.w1.samsung.com (mailout4.w1.samsung.com [210.118.77.14]) by dpdk.org (Postfix) with ESMTP id 294C35A5D for ; Thu, 31 Dec 2015 14:47:04 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout4.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O0800JOS6AE5H80@mailout4.w1.samsung.com> for dev@dpdk.org; Thu, 31 Dec 2015 13:47:02 +0000 (GMT) X-AuditID: cbfec7f5-f79b16d000005389-70-568531d69173 Received: from eusync2.samsung.com ( [203.254.199.212]) by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id F7.16.21385.6D135865; Thu, 31 Dec 2015 13:47:02 +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 <0O08003CG6ADVI30@eusync2.samsung.com>; Thu, 31 Dec 2015 13:47:02 +0000 (GMT) From: Pavel Fedin To: "'Tan, Jianfeng'" , dev@dpdk.org References: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> <002401d143af$38a6fa60$a9f4ef20$@samsung.com> <002c01d143b7$568aace0$03a006a0$@samsung.com> In-reply-to: Date: Thu, 31 Dec 2015 16:47:01 +0300 Message-id: <003b01d143d1$ba4895c0$2ed9c140$@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: AQG9CCSBEyyw7dOXpyvuWj3KD0VyOAKSxP3UAeaqL4ICeMdKeAFj1QbGAeJKf/Oeu87icA== Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsVy+t/xK7rXDFvDDJZ1Slq8+7SdyaJ79hc2 ByaPXwuWsnos3vOSKYApissmJTUnsyy1SN8ugStjxrRv7AWLRComt91jaWB8JtjFyMEhIWAi seqLWhcjJ5ApJnHh3no2kLCQwFJGidmFXYxcQOZ3Rol/E64ygtSwCahLnP76gQXEFhGwkXg5 fQ8riA1UxCTx8ospiM0pECZx+fAusHphATuJ75+vsoDMZBFQlfj+DayEV8BS4kDvfzYIW1Di x+R7YCOZBbQk1u88zgRhy0tsXvOWGeI0BYkdZ18zQqyNkLg6aQMbRI2IxLR/95gnMArOQjJq FpJRs5CMmoWkZQEjyypG0dTS5ILipPRcI73ixNzi0rx0veT83E2MkAD+uoNx6TGrQ4wCHIxK PLw/MlrChFgTy4orcw8xSnAwK4nw2hcDhXhTEiurUovy44tKc1KLDzFKc7AoifPO3PU+REgg PbEkNTs1tSC1CCbLxMEp1cDoqf+AQfXoO5/fLhJSb/J0AubPNpjxKK1pWve1GLcK447kA0Hx ehsubZl76te8omQT1Urv5iDlm/KPVf/+WXvzzdfXcw/NZrxSGqt1+enewhfm/M8C43Y/9K2Y eqbu05OVUbw5R3ZO3tIwmU/zSs6jM27ibooK6zlTp17Pc3hXaOJ4xmHOicOvlFiKMxINtZiL ihMBhTq8KlwCAAA= Subject: Re: [dpdk-dev] [RFC 0/5] virtio support for container 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, 31 Dec 2015 13:47:04 -0000 Hello! > > a) ovs_in_container does not send VHOST_USER_SET_MEM_TABLE > Please check if rte_eth_dev_start() is called. > (rte_eth_dev_start -> virtio_dev_start -> vtpci_reinit_complete -> kick_all_vq) I've figured out what happened, and it's my fault only :( I have modified your patchset and added --shared-mem option. And forgot to specify it to gdb :) Without it memory is not shared, and rte_memseg_info_get() returned fd = -1. And if you put it into control message for sendmsg(), you get your -EBADF. So please ignore this. But, nevertheless, ovs in container still dies with: --- cut --- Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff97fff700 (LWP 3866)] virtio_recv_mergeable_pkts (rx_queue=0x7fffd46a9a80, rx_pkts=0x7fff97ffe850, nb_pkts=32) at /home/p.fedin/dpdk/drivers/net/virtio/virtio_rxtx.c:683 683 /home/p.fedin/dpdk/drivers/net/virtio/virtio_rxtx.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 virtio_recv_mergeable_pkts (rx_queue=0x7fffd46a9a80, rx_pkts=0x7fff97ffe850, nb_pkts=32) at /home/p.fedin/dpdk/drivers/net/virtio/virtio_rxtx.c:683 #1 0x0000000000669ee8 in rte_eth_rx_burst (nb_pkts=32, rx_pkts=0x7fff97ffe850, queue_id=0, port_id=0 '\000') at /home/p.fedin/dpdk/build/include/rte_ethdev.h:2510 #2 netdev_dpdk_rxq_recv (rxq_=, packets=0x7fff97ffe850, c=0x7fff97ffe84c) at lib/netdev-dpdk.c:1033 #3 0x00000000005e8ca1 in netdev_rxq_recv (rx=, buffers=buffers@entry=0x7fff97ffe850, cnt=cnt@entry=0x7fff97ffe84c) at lib/netdev.c:654 #4 0x00000000005cb338 in dp_netdev_process_rxq_port (pmd=pmd@entry=0x7fffac7f8010, rxq=, port=, port=) at lib/dpif-netdev.c:2510 #5 0x00000000005cc649 in pmd_thread_main (f_=0x7fffac7f8010) at lib/dpif-netdev.c:2671 #6 0x0000000000628424 in ovsthread_wrapper (aux_=) at lib/ovs-thread.c:340 #7 0x00007ffff70f660a in start_thread () from /lib64/libpthread.so.0 #8 0x00007ffff6926bbd in clone () from /lib64/libc.so.6 (gdb) --- cut --- and l2fwd does not reproduce this. So, let's wait until 11.01.2016. And happy New Year to everybody who reads it (and who doesn't) :) Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia