From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Varun <varun.kudva@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] Hyper-v support
Date: Tue, 6 Dec 2016 13:29:43 -0800 [thread overview]
Message-ID: <20161206132943.5ff2d74f@xeon-e3> (raw)
In-Reply-To: <1929209.d2FdTvr7Hj@xps13>
On Tue, 06 Dec 2016 22:25:29 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 2016-12-06 12:25, Stephen Hemminger:
> > 2016-12-01 12:21, Thomas Monjalon:
> > > 2016-11-30 14:34, Varun:
> > > > Hi,
> > > >
> > > > I would like to know if the latest DPDK (16.11) supports hyper-v?
> > > >
> > > > I couldn't find any conclusive evidence online or in dpdk roadmap. Is it
> > > > likely that we see it in 17.05?
> > >
> > > Stephen did a presentation at the last DPDK userspace summit:
> > > https://dpdksummit.com/Archive/pdf/2016Userspace/Day01-Session03-StephenHemminger-Userspace2016.pdf
> > >
> > > Stephen, please, could you confirm the expected release for Hyper-V support?
> > > A patch for the roadmap page would be great:
> > > http://dpdk.org/dev/roadmap
> >
> > Yes, the plan is the same. Since DPDK is moving target, getting merges done has been
> > a real pain. The Hyper-V UIO generic driver has just gone into upstream next tree.
>
> I don't understand what you mean.
The code from Brocade was on older release, and depended on a slightly different model
for UIO interaction. Resolving this has taken longer than expected. Also the changes from
The changes to PCI for v16.11 overlapped vmbus related changes.
next prev parent reply other threads:[~2016-12-06 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 22:34 Varun
2016-12-01 11:21 ` Thomas Monjalon
2016-12-01 11:25 ` Thomas Monjalon
2016-12-06 20:25 ` Stephen Hemminger
2016-12-06 21:25 ` Thomas Monjalon
2016-12-06 21:29 ` Stephen Hemminger [this message]
2018-05-23 19:11 Jaime Zelaya
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=20161206132943.5ff2d74f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=varun.kudva@gmail.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).