Thread (18 messages) 18 messages, 9 authors, 2017-06-19

Re: [PATCH] maintainers: claim responsability for xen

From: Thomas Monjalon <hidden>
Date: 2017-05-04 22:04:24

Ping

The Xen dom0 support in DPDK seems dead.

Reminder:
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 (9 months ago) was to give more time for feedbacks:
        http://dpdk.org/ml/archives/dev/2016-July/044847.html


23/02/2017 09:49, Thomas Monjalon:
2017-02-20 15:33, Joao Martins:
quoted
On 02/17/2017 04:07 PM, Konrad Rzeszutek Wilk wrote:
quoted
On Thu, Feb 16, 2017 at 10:51:44PM +0100, Vincent JARDIN wrote:
quoted
Le 16/02/2017 à 14:36, Konrad Rzeszutek Wilk a écrit :
quoted
quoted
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?
OK, see attached - I should note that its a WIP as Konrad noted, but once the
staging grants work is finished, the code would be improved to have it in better
shape (as well as in feature parity) for a proper RFC [and adhering to the
project coding style].
Excuse my ignorance on Xen.
Is xen-netback for Dom0?
Is the DPDK Dom0 support working and useful?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help