Hi Thomas, > -----Original Message----- > From: Thomas Monjalon <tho...@monjalon.net> > Sent: Thursday, January 14, 2021 12:52 AM > To: Xia, Chenbo <chenbo....@intel.com> > Cc: dev@dpdk.org; david.march...@redhat.com; step...@networkplumber.org; > Liang, > Cunming <cunming.li...@intel.com>; Lu, Xiuchun <xiuchun...@intel.com>; Li, > Miao <miao...@intel.com>; Wu, Jingjing <jingjing...@intel.com>; > techbo...@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v2 0/8] Introduce emudev library and iavf > emudev driver > > 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 works fine. > > 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. OK. > In the meantime, the draft repository will help getting interest, > testing, reviews and opinions. Thanks for doing this 😊 Cheers, Chenbo > >
