All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: 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>,
	Vincent JARDIN <vincent.jardin@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim responsability for xen
Date: Thu, 23 Feb 2017 09:49:15 +0100	[thread overview]
Message-ID: <4346357.L5KG7J6tvv__27583.9159185582$1487839831$gmane$org@xps13> (raw)
In-Reply-To: <58AB0C46.5020601@oracle.com>

2017-02-20 15:33, Joao Martins:
> On 02/17/2017 04:07 PM, Konrad Rzeszutek Wilk wrote:
> > 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?
> 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?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-02-23  8:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  7:38 [PATCH] maintainers: claim responsability for xen Jianfeng Tan
2016-11-09 22:03 ` Thomas Monjalon
2016-11-10 18:59   ` [dpdk-dev] " Konrad Rzeszutek Wilk
2016-11-10 18:59   ` Konrad Rzeszutek Wilk
2016-11-10 20:49     ` [dpdk-dev] " Tan, Jianfeng
2016-11-10 20:49     ` Tan, Jianfeng
2017-02-16 11:06       ` [dpdk-dev] " Thomas Monjalon
2017-02-16 11:06       ` Thomas Monjalon
2017-02-16 13:02         ` Vincent JARDIN
2017-02-16 13:02         ` [dpdk-dev] " Vincent JARDIN
2017-02-16 13:36         ` Konrad Rzeszutek Wilk
2017-02-16 16:17           ` Jan Blunck
2017-02-16 16:17           ` [dpdk-dev] " Jan Blunck
2017-02-16 21:51           ` Vincent JARDIN
2017-02-17 16:07             ` [dpdk-dev] " Konrad Rzeszutek Wilk
2017-02-20  9:56               ` Jan Blunck
2017-02-20 17:36                 ` Joao Martins
2017-02-20 17:36                 ` [dpdk-dev] " Joao Martins
2017-02-20  9:56               ` Jan Blunck
2017-02-20 15:33               ` Joao Martins
2017-02-23  8:49                 ` Thomas Monjalon [this message]
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
2017-06-19 13:22                       ` [dpdk-dev] " Thomas Monjalon
2017-05-11 11:41                     ` Tan, Jianfeng
2017-05-04 22:04                   ` Thomas Monjalon
2017-02-16 21:51           ` Vincent JARDIN

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='4346357.L5KG7J6tvv__27583.9159185582$1487839831$gmane$org@xps13' \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=joao.m.martins@oracle.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 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.