DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Jim Holland (jimholla)" <jimholla@cisco.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Xen/netfront
Date: Tue, 31 Jul 2018 11:10:02 -0700	[thread overview]
Message-ID: <20180731111002.576ee613@xeon-e3> (raw)
In-Reply-To: <460775e7508f4fca9f906a70a046b77f@XCH-ALN-015.cisco.com>

On Tue, 31 Jul 2018 17:59:08 +0000
"Jim Holland (jimholla)" <jimholla@cisco.com> wrote:

> Hi,
> 
> Is there a recommended solution for DPDK support for netfront in Xen?
> 
> Jim

I do know Brocade/Vyatta did a driver, but it was never merged.
Xen has a number of memory restrictions that make it hard.
The DPDK support for Xen DOM-0 was dropped in recent releases because
no one was maintaining (or using) it.

      reply	other threads:[~2018-07-31 18:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 17:59 Jim Holland (jimholla)
2018-07-31 18:10 ` Stephen Hemminger [this message]

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=20180731111002.576ee613@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=jimholla@cisco.com \
    --cc=users@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).