From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 99F41A04B5;
	Wed, 13 Jan 2021 17:52:28 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 1E6AE140E23;
	Wed, 13 Jan 2021 17:52:28 +0100 (CET)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com
 [64.147.123.21])
 by mails.dpdk.org (Postfix) with ESMTP id 748B6140E18;
 Wed, 13 Jan 2021 17:52:26 +0100 (CET)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailout.west.internal (Postfix) with ESMTP id 90E8999C;
 Wed, 13 Jan 2021 11:52:24 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162])
 by compute4.internal (MEProxy); Wed, 13 Jan 2021 11:52:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 from:to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding:content-type; s=fm3; bh=
 mc6ZT3y76BqiF08aiCMFCNKYd2fEE3UjkrLW+vwZh1A=; b=Ppy5hSem8nm3J21B
 l7uXnNZo7tqlyGh2W7ppAe0WE0LzCwpOM75T/AgGzUMNJwipYat94jf7iAGzSLVw
 ETEPn+mn//cGz9q9WITrEr/bkstEshXTNROS6g+RKGX0Zga4Hj7rwjf4cw4aMthz
 BfiNbKXWFAHjwLobiCbfAWdF/QIAWkrHUnrew8mLs6Y/W5ubAdnEFLuQlKJcVJtz
 k3iDhPhFD8rz5DP7nSR583k+ZcV/SopAZKE9nLJM9eh5PRmJGOXpOzrLaeT7aIqv
 7N6UYW8mDCHfKGkLnGFnOYsPt8ZHqTt7eQ6kncCccrIy49QfcVfXkOYGPvxlmezz
 gZO1ZA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm1; bh=mc6ZT3y76BqiF08aiCMFCNKYd2fEE3UjkrLW+vwZh
 1A=; b=TaG5HsiFTpgGVNt8wrKzPm4jw2/vxOCnwPoQBYrxrSQh+dRzknAn0G6Ra
 3xMNQbaKF3UY4nqXyijqlRMc+hojjcZxDvEPtWHh4UPMT4PoKkDB6nqepxeTp8gl
 aKSDhK194VYwpm6Omb2Rfq+oQoaiY3yjA887nykVek5IwvTgSamFiNvCyxjxWN1g
 DYIW7fIZBgYarw06QJqYQwxYACpXLuuQOu3qBnhq6z//Yg9jQ7MayrHJepI9nTCa
 6WpfGNGVBUBmovofUELWHh5PvXwE1oVO2ipvz0/M+n3X9xydWwWf8QACOJzzamIb
 DwsLsZbg7itp4RQ9rqDfJpAkUfNzA==
X-ME-Sender: <xms:RyX_X8L0H4vm0BPr6xgBrOGs8f9Zi0nq_TTmsuuEf-05JOFxDdv2xw>
 <xme:RyX_Xwdu8W4FY0SWw_KFA39osh8CxRYqaHpWj43RXJyNCfnS8-DlFKUTL-Ld7aEYN
 Cqvr_5ff3MAPC0F3w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedukedrtdefgdelfecutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
 uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc
 fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs
 ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf
 frrghtthgvrhhnpeffvdffjeeuteelfeeileduudeugfetjeelveefkeejfeeigeehteff
 vdekfeegudenucffohhmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvd
 dtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr
 ohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght
X-ME-Proxy: <xmx:RyX_X73VroH9kobT_XoW-NPaa0r0H5d5RL70yd-YHtNtRf5Q4bkJHQ>
 <xmx:RyX_XxjHhu1vmkuEiqv8vsCbeHEc5KUB0w9ozt4wI5cdO0WIQNeM7A>
 <xmx:RyX_X5Rd4MeFGMX3rQ6brypo_xd1N15gSaq6XhuijjhWuvXUG5bz5w>
 <xmx:SCX_X_4Ho7zo6LoU5HLuZxM6KAMfCkZmFf1HPvZm9p3M5tkT8ghL0Q>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id BB5CE240064;
 Wed, 13 Jan 2021 11:52:22 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Chenbo Xia <chenbo.xia@intel.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, stephen@networkplumber.org,
 cunming.liang@intel.com, xiuchun.lu@intel.com, miao.li@intel.com,
 jingjing.wu@intel.com, techboard@dpdk.org
Date: Wed, 13 Jan 2021 17:52:21 +0100
Message-ID: <3929200.M8Uy5f1AHv@thomas>
In-Reply-To: <20201219062806.56477-1-chenbo.xia@intel.com>
References: <20201218074736.93999-1-chenbo.xia@intel.com>
 <20201219062806.56477-1-chenbo.xia@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v2 0/8] Introduce emudev library and iavf
 emudev driver
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

19/12/2020 07:27, Chenbo Xia:
> This series introduces a new device abstraction called emudev for emulated
> devices. A new library (librte_emudev) is implemented. The first emudev
> driver is also introduced, which emulates Intel Adaptive Virtual Function
> (iavf) as a software network device.
> 
> This series has a dependency on librte_vfio_user patch series:
> http://patchwork.dpdk.org/cover/85389/
> 
> Background & Motivation 
> -----------------------
> The disaggregated/multi-process QEMU is using VFIO-over-socket/vfio-user
> as the main transport mechanism to disaggregate IO services from QEMU.
> Therefore, librte_vfio_user is introduced in DPDK to accommodate
> emulated devices for high performance I/O. Although vfio-user library
> provides possibility of emulating devices in DPDK, DPDK does not have
> a device abstraction for emulated devices. A good device abstraction will
> be useful for applications or high performance data path driver. With
> this consideration, emudev library is designed and implemented. It also
> make it possbile to keep modular design on emulated devices by implementing
> data path related logic in a standalone driver (e.g., an ethdev driver)
> and keeps the unrelated logic in the emudev driver.


As voted today in the Technical Board meeting,
there will be a draft repository to host this initiative.
A proposed name for the git tree is:
	dpdk-draft-emudev
Feel free to propose a better name.

This series cannot be merged in the main repository
until the Qemu specification is made official.
When Qemu part will be complete, we can assume more reviews
of the DPDK related code.
In the meantime, the draft repository will help getting interest,
testing, reviews and opinions.