From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by dpdk.org (Postfix) with ESMTP id D8B05682E for ; Wed, 27 Aug 2014 08:05:21 +0200 (CEST) Received: by mail-pa0-f54.google.com with SMTP id fa1so25348540pad.27 for ; Tue, 26 Aug 2014 23:09:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OMgF4bAOhcZD+35ncgviKMRklqzOgkJ7SX5oKcYtxJc=; b=ZpbSv4abnj6gI5jlVKnACUx0WLg6vrRK+4ACLYRfHPYH+DA0WdErmaYm2JfQrWWSrX lDUCUUKvzjzqcBcXQmoyTKqQDHoPXYqW4SQGT9vkfFh+Z6cMAmehZSRqJHxwJxKPuxgs 2w3dt9corg+icefX7wIQBm9PTom7M3caJQW5PvUrLzwr4HjpB3lKdKURySOozJ+9BhE9 /rq01L/Qxxnl0UjkxbTFXGuEeNZEA833612C1RjhYl6/Pk4mKbXKB/AKOQLDEvD3Jkn7 uqg81RyBGbECBUL0sYURHnd25WphRiXcY3kb6feoMvFCuT/DLJ/k3K2yJAOzdwOJhFO7 pCtg== X-Gm-Message-State: ALoCoQlovL58L2TjdtgvM5nACwO5o7+nz5/SZw85rhZFXRqJ+P26FZxM9/GawKfGVPzPb86Ojf8r X-Received: by 10.67.14.97 with SMTP id ff1mr42573397pad.109.1409119763886; Tue, 26 Aug 2014 23:09:23 -0700 (PDT) Received: from [10.16.129.101] (napt.igel.co.jp. [219.106.231.132]) by mx.google.com with ESMTPSA id ps6sm5286468pbb.56.2014.08.26.23.09.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Aug 2014 23:09:23 -0700 (PDT) Message-ID: <53FD7611.5000709@igel.co.jp> Date: Wed, 27 Aug 2014 15:09:21 +0900 From: "Tetsuya.Mukawa" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Ouyang, Changchun" , "dev@dpdk.org" References: <53FD60FD.5090903@igel.co.jp> <53FD6C4E.5040907@igel.co.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Katsuya MATSUBARA , "nakajima.yoshihiro@lab.ntt.co.jp" , Hitoshi Masutani Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support into DPDK vhost library 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, 27 Aug 2014 06:05:22 -0000 Hi Ouyang, (2014/08/27 15:00), Ouyang, Changchun wrote: > Yes, it doesn't matter which one is faster for virtio device creation > and destroy, as it is not in data path. I agree with you. Thanks, Tetsuya >> Thanks, >> Tetsuya >> >> >>> Regards, >>> Changchun >>> >>>> -----Original Message----- >>>> From: Tetsuya.Mukawa [mailto:mukawa@igel.co.jp] >>>> Sent: Wednesday, August 27, 2014 12:39 PM >>>> To: Ouyang, Changchun; dev@dpdk.org >>>> Cc: Xie, Huawei; Katsuya MATSUBARA; nakajima.yoshihiro@lab.ntt.co.jp; >>>> Hitoshi Masutani >>>> Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user >>>> support into DPDK vhost library >>>> >>>> >>>> (2014/08/27 9:43), Ouyang, Changchun wrote: >>>>> Do we have performance comparison between both implementation? >>>> Hi Changchun, >>>> >>>> If DPDK applications are running on both guest and host side, the >>>> performance should be almost same, because while transmitting data >>>> virt queues are accessed by virtio-net PMD and libvhost. In libvhost, >>>> the existing vhost implementation and a vhost-user implementation >>>> will shares or uses same code to access virt queues. So I guess the >>>> performance will be almost same. >>>> >>>> Thanks, >>>> Tetsuya >>>> >>>> >>>>> Thanks >>>>> Changchun >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Xie, Huawei >>>>> Sent: Tuesday, August 26, 2014 7:06 PM >>>>> To: dev@dpdk.org >>>>> Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user >>>>> support into DPDK vhost library >>>>> >>>>> Hi all: >>>>> We are implementing qemu official vhost-user interface into DPDK >>>>> vhost >>>> library, so there would be two coexisting implementations for user >>>> space vhost backend. >>>>> Pro and cons in my mind: >>>>> Existing solution: >>>>> Pros: works with qemu version before 2.1; Cons: depends on eventfd >>>> proxy kernel module and extra maintenance effort Qemu vhost-user: >>>>> Pros: qemu official us-vhost interface; Cons: only available >> after >>>> qemu 2.1 >>>>> BR. >>>>> huawei