From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 403C38D8F for ; Thu, 31 Dec 2015 11:02:50 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP; 31 Dec 2015 02:02:49 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,503,1444719600"; d="scan'208";a="21672410" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga004.fm.intel.com with ESMTP; 31 Dec 2015 02:02:48 -0800 Received: from fmsmsx117.amr.corp.intel.com (10.18.116.17) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 31 Dec 2015 02:02:48 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx117.amr.corp.intel.com (10.18.116.17) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 31 Dec 2015 02:02:48 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.133]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.183]) with mapi id 14.03.0248.002; Thu, 31 Dec 2015 18:02:46 +0800 From: "Tan, Jianfeng" To: Pavel Fedin , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC 0/5] virtio support for container Thread-Index: AdFC5lAx4gxjgPHsRda0ClGnzG0GiAAwk/4w//+HE4D//3X7sA== Date: Thu, 31 Dec 2015 10:02:45 +0000 Message-ID: References: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> <002401d143af$38a6fa60$a9f4ef20$@samsung.com> In-Reply-To: <002401d143af$38a6fa60$a9f4ef20$@samsung.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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:02:50 -0000 > -----Original Message----- > From: Pavel Fedin [mailto:p.fedin@samsung.com] > Sent: Thursday, December 31, 2015 5:40 PM > To: Tan, Jianfeng; dev@dpdk.org > Subject: RE: [dpdk-dev] [RFC 0/5] virtio support for container >=20 > Hello! >=20 > > First of all, when you say openvswitch, are you referring to ovs-dpdk? >=20 > 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. >=20 > > And can you detail your test case? Like, how do you want ovs_on_host an= d > 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? >=20 > vhost port. i. e. >=20 > | > LOCAL------dpdkvhostuser<----+---->cvio----->LOCAL > ovs | ovs > | > host | container >=20 > 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. Yes, this case is exactly suited for this patchset. Before you start another ovs_in_container, previous ones get killed? If so,= vhost information in ovs_on_host will be wiped as the unix socket is broken. And by the way, ovs just allows one virtio for one vhost port, much differe= nt from the exmpale, vhost-switch. Thanks, Jianfeng =20 > Those messages about memory pool already being present are perhaps OK. >=20 > Kind regards, > Pavel Fedin > Expert Engineer > Samsung Electronics Research center Russia >=20