From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Blunck <Jan.Blunck@brocade.com>, sergio.gonzalez.monroy@intel.com
Cc: dev@dpdk.org, huawei.xie@intel.com, huilongx.xu@intel.com,
thiagocmartinsc@gmail.com
Subject: Re: [dpdk-dev] DPDK on Xen maintenance
Date: Wed, 20 Jul 2016 18:51:56 +0200 [thread overview]
Message-ID: <9951678.mJBNUYIUdn@xps13> (raw)
In-Reply-To: <1468405836.28473.15.camel@brocade.com>
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.
prev parent reply other threads:[~2016-07-20 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 9:34 Thomas Monjalon
2016-07-13 10:30 ` Jan Blunck
2016-07-20 16:51 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9951678.mJBNUYIUdn@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=Jan.Blunck@brocade.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=huilongx.xu@intel.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=thiagocmartinsc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).