From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>,
Joao Martins <joao.m.martins@oracle.com>
Cc: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
yuanhan.liu@linux.intel.com, dev@dpdk.org,
bruce.richardson@intel.com,
Xen-devel <xen-devel@lists.xenproject.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim responsability for xen
Date: Fri, 17 Feb 2017 11:07:31 -0500 [thread overview]
Message-ID: <20170217160731.GA30539@char.us.ORACLE.com> (raw)
In-Reply-To: <b770194a-e4de-0aca-e41e-2aa49e1c1b4c@6wind.com>
On Thu, Feb 16, 2017 at 10:51:44PM +0100, Vincent JARDIN wrote:
> Le 16/02/2017 à 14:36, Konrad Rzeszutek Wilk a écrit :
> > > 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.
>
> Please, do you have URLs/pointers about it? It would be interesting to share
> it with DPDK community too.
Joao, would it be possible to include an tarball of the patches? I know
they are no in the right state with the review of the staging
grants API - they are incompatible, but it may help folks to get
a feel for what DPDK APIs you used?
Staging grants API:
https://lists.xenproject.org/archives/html/xen-devel/2016-12/msg01878.html
>
> Best regards,
> Vincent
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-17 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1478504326-68105-1-git-send-email-jianfeng.tan@intel.com>
[not found] ` <10491202.nlFsPbIJhh@xps13>
2016-11-10 18:59 ` [dpdk-dev] [PATCH] maintainers: claim responsability for xen Konrad Rzeszutek Wilk
[not found] ` <CACJDEmqC7T5O=zF6SOsmfOizRXYM+e7nmbY=2VA4aJ13tkAS-w@mail.gmail.com>
2016-11-10 20:49 ` Tan, Jianfeng
[not found] ` <83319780-26e9-afb6-74cd-20c07dad04a7@intel.com>
2017-02-16 11:06 ` Thomas Monjalon
[not found] ` <1915354.hxpEe7tUeI@xps13>
2017-02-16 13:02 ` Vincent JARDIN
2017-02-16 13:36 ` Konrad Rzeszutek Wilk
2017-02-16 16:17 ` Jan Blunck
2017-02-16 21:51 ` Vincent JARDIN
[not found] ` <b770194a-e4de-0aca-e41e-2aa49e1c1b4c@6wind.com>
2017-02-17 16:07 ` Konrad Rzeszutek Wilk [this message]
2017-02-20 9:56 ` Jan Blunck
2017-02-20 15:33 ` Joao Martins
2017-02-23 8:49 ` Thomas Monjalon
[not found] ` <4346357.L5KG7J6tvv@xps13>
2017-05-04 22:04 ` Thomas Monjalon
[not found] ` <1596758.olymjc7Tvq@xps>
2017-05-11 11:41 ` Tan, Jianfeng
[not found] ` <ED26CBA2FAD1BF48A8719AEF02201E36511C7F5A@SHSMSX103.ccr.corp.intel.com>
2017-06-19 13:22 ` Thomas Monjalon
[not found] ` <CALe+Z0153tPoor2HpNXOX57t4E_coHaNcVLnwFtL=6LFE0nr7A@mail.gmail.com>
2017-02-20 17:36 ` Joao Martins
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=20170217160731.GA30539@char.us.ORACLE.com \
--to=konrad.wilk@oracle.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=thomas.monjalon@6wind.com \
--cc=vincent.jardin@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).