From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
dev@dpdk.org, bruce.richardson@intel.com,
yuanhan.liu@linux.intel.com,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim responsability for xen
Date: Thu, 16 Feb 2017 08:36:58 -0500 [thread overview]
Message-ID: <20170216133657.GB14695@dhcp-whq-twvpn-1-vpnpool-10-159-157-38.vpn.oracle.com> (raw)
In-Reply-To: <1915354.hxpEe7tUeI@xps13>
On Thu, Feb 16, 2017 at 12:06:18PM +0100, Thomas Monjalon wrote:
> 2016-11-11 04:49, Tan, Jianfeng:
> > Hi Thomas and Konrad,
> >
> > On 11/11/2016 2:59 AM, Konrad Rzeszutek Wilk wrote:
> > > On Wed, Nov 9, 2016 at 5:03 PM, Thomas Monjalon wrote:
> > >> 2016-11-07 07:38, Jianfeng Tan:
> > >>> As some users are still using xen as the hypervisor, I suggest to
> > >>> continue support for xen in DPDK. And from 16.11, I will be the
> > >>> maintainer of all xen-related files.
> > >>>
> > >>> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> > >> Applied
> > >>
> > >> Please Jianfeng, could you start your new role by sending a status
> > >> of Xen dom0 support in DPDK? I think there are some issues in latest releases.
> >
> > Yes, I'm on this. And hope to send out update in the next week.
> >
> > > Pls also CC me and xen-devel@lists.xenproject.org if possible.
> >
> > Glad to do that.
> >
> > Thanks,
> > Jianfeng
>
> Any news about Xen dom0 status in DPDK?
>
> I think there is not enough interest for Xen dom0 in the DPDK community.
> 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
> http://dpdk.org/ml/archives/dev/2016-July/044376.html
>
> The request (6 month ago) was to give more time for feedbacks:
> http://dpdk.org/ml/archives/dev/2016-July/044847.html
>
> Is it time now to officially remove Dom0 support?
So we do have an prototype implementation of netback but it is waiting
for review of xen-devel to the spec.
And I believe the implementation does utilize some of the dom0
parts of code in DPDK.
next prev parent reply other threads:[~2017-02-16 13:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 7:38 Jianfeng Tan
2016-11-09 22:03 ` Thomas Monjalon
2016-11-10 18:59 ` Konrad Rzeszutek Wilk
2016-11-10 20:49 ` Tan, Jianfeng
2017-02-16 11:06 ` Thomas Monjalon
2017-02-16 13:02 ` Vincent JARDIN
2017-02-16 13:36 ` Konrad Rzeszutek Wilk [this message]
2017-02-16 16:17 ` Jan Blunck
2017-02-16 21:51 ` Vincent JARDIN
2017-02-17 16:07 ` Konrad Rzeszutek Wilk
2017-02-20 9:56 ` Jan Blunck
2017-02-20 17:36 ` Joao Martins
2017-02-20 15:33 ` Joao Martins
2017-02-23 8:49 ` Thomas Monjalon
2017-02-23 20:10 ` Martinx - ジェームズ
2017-05-04 22:04 ` Thomas Monjalon
2017-05-11 11:41 ` Tan, Jianfeng
2017-06-19 13:22 ` 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=20170216133657.GB14695@dhcp-whq-twvpn-1-vpnpool-10-159-157-38.vpn.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=konrad@kernel.org \
--cc=thomas.monjalon@6wind.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yuanhan.liu@linux.intel.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).