From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 3186F9432 for ; Wed, 6 Jan 2016 06:47:30 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP; 05 Jan 2016 21:47:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,528,1444719600"; d="scan'208";a="875438189" Received: from shwdeisgchi083.ccr.corp.intel.com (HELO [10.239.67.119]) ([10.239.67.119]) by fmsmga001.fm.intel.com with ESMTP; 05 Jan 2016 21:47:30 -0800 To: Pavel Fedin , dev@dpdk.org References: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> <002401d143af$38a6fa60$a9f4ef20$@samsung.com> <002c01d143b7$568aace0$03a006a0$@samsung.com> <000301d143e1$6c5c0e90$45142bb0$@samsung.com> From: "Tan, Jianfeng" Message-ID: <568CAA70.7070201@intel.com> Date: Wed, 6 Jan 2016 13:47:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <000301d143e1$6c5c0e90$45142bb0$@samsung.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 06 Jan 2016 05:47:30 -0000 On 12/31/2015 11:39 PM, Pavel Fedin wrote: > Hello! > > Last minute note. I have found the problem but have no time to research and fix it. > It happens because ovs first creates the device, starts it, then stops it, and reconfigures queues. The second queue allocation > happens from within netdev_set_multiq(). Then ovs restarts the device and proceeds to actually using it. > But, queues are not initialized properly in DPDK after the second allocation. Because of this thing: > > /* On restart after stop do not touch queues */ > if (hw->started) > return 0; Hi Fedin, As you see, I also think it is a bug. A device should be ok to start/stop/start... I already send a patch to fix this. http://dpdk.org/ml/archives/dev/2016-January/031010.html Thanks, Jianfeng > > It keeps us away from calling virtio_dev_rxtx_start(), which should in turn call virtio_dev_vring_start(), which calls > vring_init(). So, VIRTQUEUE_NUSED() dies badly because vq->vq_ring all contains NULLs. > See you all after 10th. And happy New Year again! > >