From: Jan Blunck <Jan.Blunck@brocade.com>
To: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "huawei.xie@intel.com" <huawei.xie@intel.com>,
"huilongx.xu@intel.com" <huilongx.xu@intel.com>,
"thiagocmartinsc@gmail.com" <thiagocmartinsc@gmail.com>
Subject: Re: [dpdk-dev] DPDK on Xen maintenance
Date: Wed, 13 Jul 2016 10:30:36 +0000 [thread overview]
Message-ID: <1468405836.28473.15.camel@brocade.com> (raw)
In-Reply-To: <1795705.pPV7SVCssA@xps13>
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:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__dpdk.org_ml
> _archives_dev_2016-
> 2DJuly_043760.html&d=CwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=eGq7Pg5OSP440n
> QUcjb02I48YXd7Ce6OiSj9BMaGZiE&m=98n7rM-Tjze4nm2MUpU8Etvo5lAB-
> oe0KXsst27ujkw&s=AHzBPDmKhqbsIc8pb2x_s7ShJvDhf93AsXRAm43EXlM&e=
> 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.
> 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.
>
> Thanks
next prev parent reply other threads:[~2016-07-13 10:30 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 [this message]
2016-07-20 16:51 ` Thomas Monjalon
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=1468405836.28473.15.camel@brocade.com \
--to=jan.blunck@brocade.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=huilongx.xu@intel.com \
--cc=thiagocmartinsc@gmail.com \
--cc=thomas.monjalon@6wind.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).