All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: huawei.xie@intel.com, Jan Blunck <jan.blunck@brocade.com>,
	huilongx.xu@intel.com, Thiago Martins <thiagocmartinsc@gmail.com>
Subject: DPDK on Xen maintenance
Date: Tue, 12 Jul 2016 11:34:05 +0200	[thread overview]
Message-ID: <1795705.pPV7SVCssA@xps13> (raw)

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

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

             reply	other threads:[~2016-07-12  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  9:34 Thomas Monjalon [this message]
2016-07-13 10:30 ` DPDK on Xen maintenance Jan Blunck
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=1795705.pPV7SVCssA@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    --cc=huilongx.xu@intel.com \
    --cc=jan.blunck@brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.