From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com [210.118.77.13]) by dpdk.org (Postfix) with ESMTP id BF44B8DB1 for ; Thu, 31 Dec 2015 10:40:03 +0100 (CET) Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O0700LUOUUQJN20@mailout3.w1.samsung.com> for dev@dpdk.org; Thu, 31 Dec 2015 09:40:02 +0000 (GMT) X-AuditID: cbfec7f4-f79026d00000418a-ee-5684f7f24dff Received: from eusync4.samsung.com ( [203.254.199.214]) by eucpsbgm1.samsung.com (EUCPMTA) with SMTP id 78.08.16778.2F7F4865; Thu, 31 Dec 2015 09:40:02 +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 <0O0700AG0UUPJH40@eusync4.samsung.com>; Thu, 31 Dec 2015 09:40:02 +0000 (GMT) From: Pavel Fedin To: "'Tan, Jianfeng'" , dev@dpdk.org References: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> In-reply-to: Date: Thu, 31 Dec 2015 12:40:01 +0300 Message-id: <002401d143af$38a6fa60$a9f4ef20$@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: AQG9CCSBEyyw7dOXpyvuWj3KD0VyOAKSxP3Unvi2oLA= Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsVy+t/xa7qfvreEGfyYy2zx7tN2Jovu2V/Y HJg8fi1YyuqxeM9LpgCmKC6blNSczLLUIn27BK6ML/e3MxY0cFY8+J3UwLifrYuRk0NCwERi 7oVdjBC2mMSFe+vB4kICSxklLk8u6WLkArK/M0p03D7CBJJgE1CXOP31AwuILSJgI/Fy+h5W iIZmRomfM8GaOQXCJLZ1LmIHsYUF7CS+f74KVs8ioCrxsmM6M4jNK2Ap8efXfyhbUOLH5Htg NcwCWhLrdx5ngrDlJTavecsMcZyCxI6zrxkh9lpJPJ78gB2iRkRi2r97zBMYBWchGTULyahZ SEbNQtKygJFlFaNoamlyQXFSeq6hXnFibnFpXrpecn7uJkZIEH/Zwbj4mNUhRgEORiUe3gVp LWFCrIllxZW5hxglOJiVRHjti4FCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeefueh8iJJCeWJKa nZpakFoEk2Xi4JRqYGRV0HJl43y5+3ZduWtLgHLC1m9GT+rmH7ip5RkpL3ikteRgkkyUyRy3 DX6Mf7NXSX/o2bbyzJoVQsdnMJvcnnn1Wn1D+QeblnVVO5R2hFhpLagzOVH47NVLvu1net4q Zh3hnjRratj7xmePnuptYWiaGzZd7bRJRbei0wt+njnLwo2fzPwscl6JpTgj0VCLuag4EQBR bTZkXgIAAA== 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 09:40:03 -0000 Hello! > First of all, when you say openvswitch, are you referring to ovs-dpdk? I am referring to mainline ovs, compiled with dpdk, and using userspace dataplane. AFAIK ovs-dpdk is early Intel fork, which is abandoned at the moment. > And can you detail your test case? Like, how do you want ovs_on_host and ovs_in_container to > be connected? > Through two-direct-connected physical NICs, or one vhost port in ovs_on_host and one virtio > port in ovs_in_container? vhost port. i. e. | LOCAL------dpdkvhostuser<----+---->cvio----->LOCAL ovs | ovs | host | container By this time i advanced in my research. ovs not only crashes by itself, but manages to crash host side. It does this by doing reconfiguration sequence without sending VHOST_USER_SET_MEM_TABLE, therefore host-side ovs tries to refer old addresses and dies badly. Those messages about memory pool already being present are perhaps OK. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia