From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tan, Jianfeng" Subject: Re: [PATCH] maintainers: claim responsability for xen Date: Thu, 11 May 2017 11:41:05 +0000 Message-ID: References: <1478504326-68105-1-git-send-email-jianfeng.tan@intel.com> <58AB0C46.5020601@oracle.com> <4346357.L5KG7J6tvv@xps13> <1596758.olymjc7Tvq@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: Konrad Rzeszutek Wilk , "dev@dpdk.org" , Xen-devel To: Thomas Monjalon , Joao Martins , Konrad Rzeszutek Wilk Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 585782952 for ; Thu, 11 May 2017 13:41:10 +0200 (CEST) In-Reply-To: <1596758.olymjc7Tvq@xps> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Thomas and all, Apologize for being an unqualified maintainer. > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Friday, May 5, 2017 6:04 AM > To: Joao Martins; Konrad Rzeszutek Wilk; Tan, Jianfeng > Cc: Konrad Rzeszutek Wilk; dev@dpdk.org; Xen-devel > Subject: Re: [dpdk-dev] [PATCH] maintainers: claim responsability for xen >=20 > Ping >=20 > The Xen dom0 support in DPDK seems dead. >=20 > Reminder: > Last time we talked about, it was because of a severe bug which is not > fixed yet: > http://dpdk.org/ml/archives/dev/2016-July/044207.html For this bug, we removed the userspace memset(0) and suppose it has been do= ne by kernel, however, xen0 uses __get_free_pages() kernel API to map hugep= ages and reseve memseg, I think it makes sense to zero the hugepage for xen= 0 in rte_dom0_mm kernel module (instead of some special code for xen0 in us= erspace) to keep aligned behavior. > http://dpdk.org/ml/archives/dev/2016-July/044376.html It does not make any sense to upstream a netfront PMD before we have a netb= ack PMD, as the legacy netback driver would be the bottleneck. Anyone has p= lan on this? And a question mark keeps in my mind that is it a must to impl= ement netback in dom0? >>From another perspective, instead of using netfront/netback, we can also us= e virtio/vhost as the device model; however, xl tool in xen only supports v= host-kernel backend instead of vhost-user backend. So anyone has plan to en= hance xl tool so that we can accelerate dom0 just using vswitch like OVS-DP= DK? A third solution is to use xenvirtio as the frontend, and vhost_xen as the = backend. This solution is to use virtio ring on grant table mechanism of xe= n. Honestly, I don't even know if it still work now. And to make it more us= able, better to upstream vhost_xen inside popular vswitch like OVS-DPDK. > The request (9 months ago) was to give more time for feedbacks: > http://dpdk.org/ml/archives/dev/2016-July/044847.html Apologize again that I volunteer to maintain these files, but spend very fe= w time on this. Thanks, Jianfeng