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 251335A84 for ; Thu, 31 Dec 2015 11:38:10 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout1.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O070029XXJKNF40@mailout1.w1.samsung.com> for dev@dpdk.org; Thu, 31 Dec 2015 10:38:08 +0000 (GMT) X-AuditID: cbfec7f5-f79b16d000005389-d3-56850590e430 Received: from eusync4.samsung.com ( [203.254.199.214]) by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id E4.8C.21385.09505865; Thu, 31 Dec 2015 10:38:08 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync4.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O0700AWSXJJJH50@eusync4.samsung.com>; Thu, 31 Dec 2015 10:38:08 +0000 (GMT) From: Pavel Fedin To: "'Tan, Jianfeng'" , dev@dpdk.org References: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> <002401d143af$38a6fa60$a9f4ef20$@samsung.com> In-reply-to: Date: Thu, 31 Dec 2015 13:38:07 +0300 Message-id: <002c01d143b7$568aace0$03a006a0$@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: AQG9CCSBEyyw7dOXpyvuWj3KD0VyOAKSxP3UAeaqL4ICeMdKeJ7Vy+Bw Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsVy+t/xa7oTWFvDDP6+5Ld492k7k0X37C9s DkwevxYsZfVYvOclUwBTFJdNSmpOZllqkb5dAlfG2n1TWQvaWSraFhxkbGCcw9zFyMEhIWAi sWxRVRcjJ5ApJnHh3nq2LkYuDiGBpYwSiw/MZodwvjNKvGq6wAhSxSagLnH66wcWEFtEwEbi 5fQ9rBBFfxkl/k0+xQ6S4BQIk3g69xoziC0sYCfx/fNVsAYWAVWJM1PPg9XwClhKLL37igXC FpT4MfkemM0soCWxfudxJghbXmLzmrfMEOcpSOw4+5oRYrGbxJG5U6HqRSSm/bvHPIFRcBaS UbOQjJqFZNQsJC0LGFlWMYqmliYXFCel5xrpFSfmFpfmpesl5+duYoQE8tcdjEuPWR1iFOBg VOLh/ZHREibEmlhWXJl7iFGCg1lJhNe+GCjEm5JYWZValB9fVJqTWnyIUZqDRUmcd+au9yFC AumJJanZqakFqUUwWSYOTqkGxgX9NyV0YxtOzGLnfXLnx/PLU1b/mHnvVcbcoGqu/H3cez9t XnrPmafOwshkzY6EuqrEhwdnCE26mFjR7Sr0eiH3H943V1iXmu8qEe0s/bRtjZnaeotHLx5c Xub3efqG4CN1d3hseR1sK3QefHiVuIk/Mevid1Xjjhnhn36tX/mkem3Ljfn9N1cosRRnJBpq MRcVJwIA5uf/RGACAAA= 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 10:38:10 -0000 Hello! > Before you start another ovs_in_container, previous ones get killed? Of course. It crashes. > If so, vhost information in ovs_on_host will be wiped as the unix socket is broken. Yes. And ovs_on_host crashes because: a) ovs_in_container does not send VHOST_USER_SET_MEM_TABLE (i don't know why yet) b) set_vring_addr() does not make sure that dev->mem is set. I am preparing a patch to fix (b). Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia