DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim responsability for xen
Date: Thu, 23 Feb 2017 15:10:55 -0500	[thread overview]
Message-ID: <CAJSM8J2_FpKDL5Bob7rnWL2QRMKn3OwxfzriptX-h=sHxrf_Zw@mail.gmail.com> (raw)
In-Reply-To: <4346357.L5KG7J6tvv@xps13>

On 23 February 2017 at 03:49, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 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?
>

I'm also curious about Xen support on DPDK, mostly because I'm planning to
run DPDK Apps on Amazon EC2 and they are Xen-based...

So, sorry to ask this here but, how to use DPDK on Amazon EC2 (i.e., on top
of Xen)? Which EC2 flavor / DPDK drivers to use?

Thanks!
Thiago

  reply	other threads:[~2017-02-23 20:11 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
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 - ジェームズ [this message]
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='CAJSM8J2_FpKDL5Bob7rnWL2QRMKn3OwxfzriptX-h=sHxrf_Zw@mail.gmail.com' \
    --to=thiagocmartinsc@gmail.com \
    --cc=dev@dpdk.org \
    /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).