From: Stephen Hemminger <stephen@networkplumber.org>
To: Vithal S Mohare <vmohare@arubanetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Support for MS Hyper-v hypervisor
Date: Mon, 16 Mar 2015 23:12:49 -0700 [thread overview]
Message-ID: <CAOaVG150BaCUy4nfvuiCvQUEKvQ6mBWK35eXun5RUTbUyAmp=Q@mail.gmail.com> (raw)
In-Reply-To: <98DB008FA2AC6644B40AD8C766FAB271020CA73ECF@BOREAL.arubanetworks.com>
No DPDK 1.7.x does not support hyper-v virtual NICZ.
On Mon, Mar 16, 2015 at 9:57 PM, Vithal S Mohare <vmohare@arubanetworks.com>
wrote:
> Hi,
>
> Would like to know whether present released versions of DPDK (1.7.x)
> supports MS hyper-v hypervisor. DPDK roadmap document has it in the list
> for Version 2.1. Please confirm if we need to wait for the support till
> the release of DPDK 2.1.
>
> Thanks,
> -Vithal
>
prev parent reply other threads:[~2015-03-17 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 4:57 Vithal S Mohare
2015-03-17 6:12 ` 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='CAOaVG150BaCUy4nfvuiCvQUEKvQ6mBWK35eXun5RUTbUyAmp=Q@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=vmohare@arubanetworks.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).