From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: DPDK on Xen maintenance Date: Wed, 20 Jul 2016 18:51:56 +0200 Message-ID: <9951678.mJBNUYIUdn@xps13> References: <1795705.pPV7SVCssA@xps13> <1468405836.28473.15.camel@brocade.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, huawei.xie@intel.com, huilongx.xu@intel.com, thiagocmartinsc@gmail.com To: Jan Blunck , sergio.gonzalez.monroy@intel.com Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id E16F9377C for ; Wed, 20 Jul 2016 18:51:58 +0200 (CEST) Received: by mail-wm0-f49.google.com with SMTP id f65so183192040wmi.0 for ; Wed, 20 Jul 2016 09:51:58 -0700 (PDT) In-Reply-To: <1468405836.28473.15.camel@brocade.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-07-13 10:30, Jan Blunck: > On Di, 2016-07-12 at 11:34 +0200, Thomas Monjalon wrote: > > Hi all, > > > > We are facing some issues with Xen dom0. > > Some were fixed in RC2: > > http://dpdk.org/ml/archives/dev/2016-July/043760.html > > and there still have some other issues. > > > > It seems Xen is becoming less attractive: > > - we do not have a lot of test reports or feedbacks > > - there is no maintainer for DPDK on Xen > > - we are still waiting for the Xen netfront PMD > > Although progress is slow I'm still working on upstreaming the Xen > netfront PMD. I will continue to maintain it afterwards of course. OK thanks for the update. So you are working on using DPDK in Domu. It seems that nobody is interested in using DPDK in Dom0. There is still a bug in 16.07: http://dpdk.org/ml/archives/dev/2016-July/044207.html > > I wonder wether it still makes sense to maintain this code or not? > > In case of positive reply, it would be nice to have the name of > > someone responsible for this code, i.e. a maintainer. Given that we have no feedback on Xen Dom0, no maintainer, some bugs, and it makes memory allocation improvements harder, it sounds reasonnable to drop this code.