From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by dpdk.org (Postfix) with ESMTP id 05D415942 for ; Wed, 27 Aug 2014 08:03:44 +0200 (CEST) Received: by mail-pd0-f178.google.com with SMTP id w10so24118961pde.9 for ; Tue, 26 Aug 2014 23:07:47 -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=TQFZ/h14cMMe81x8jmhvhvpe69O9A/XzxzD91zJ+2FA=; b=CAv6FtUr0A11bpT2Wsl+3lL15cD/cSBqj33nxkk2+a1QYwndv7PkzyxBbl4z+qdloc sVnJMbFobTH5cFsnu9fiXySe/PKfnPUqmk1WJVDP7CQrc1xvDdSvq2WMnNTgMrdd7leV X8IVXgkB89HUthhszVbLU+DBHxf+l1+HZS00ZMyEspGEPVPuQpMNa43rYVJPlGJpXXLU Z/iUb7AvpajYF16VjJVAG0CuGIqlabmUP9A2eU68dbwXuKpAa8z7rRrlLjedLMfDvDik XlfqwrWa+Vu+rd2gbRpUKbP2Ojkq/EzO9VNxjWcRTzwWHn0s/uwx1W6h7E23oTVx/M7i Fp+A== X-Gm-Message-State: ALoCoQlRmrDxHNBxFksr0xNckr7+cUhKehQJtLuic/hJsdz9C06zS4WLDU6wWxuILmqDN1C4fPsE X-Received: by 10.66.221.193 with SMTP id qg1mr43278417pac.9.1409119666200; Tue, 26 Aug 2014 23:07:46 -0700 (PDT) Received: from [10.16.129.101] (napt.igel.co.jp. [219.106.231.132]) by mx.google.com with ESMTPSA id x7sm8083504pdj.36.2014.08.26.23.07.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Aug 2014 23:07:45 -0700 (PDT) Message-ID: <53FD75AF.5020201@igel.co.jp> Date: Wed, 27 Aug 2014 15:07:43 +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: "Xie, Huawei" , "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:03:45 -0000 Hi Xie, (2014/08/27 14:56), Xie, Huawei wrote: > For virtio-net device driver, there is still no difference. Existing > solution creates an eventfd module to install a fd in DPDK process > pointing to the eventfd in qemu process. In vhost-user, the UNIX > domain socket will do that work, create a new fd, install it in target > DPDK server process, and make it point to the eventfd in qemu process. Thank you for explanation. I can understand clearly. Thanks, Tetsuya >> Anyway, about device creation and destruction, the difference will come >> from transmission speed between unix domain socket and CUSE. I am not >> sure which is faster. >> >> 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