DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 0/4] Hyper-V netvsc PMD and VMBus support
Date: Fri, 11 May 2018 10:38:30 -0700	[thread overview]
Message-ID: <20180511103830.2fc721e5@xeon-e3> (raw)
In-Reply-To: <f1fe4272-c970-7164-1709-8af788238fe4@intel.com>

On Fri, 11 May 2018 17:50:37 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 5/9/2018 1:26 AM, Stephen Hemminger wrote:
> > This is a revised version of the Hyper-V native bus (VMBus)
> > and network device (netvsc) drivers. This virtual device
> > is used in Microsoft Hyper-V in Windows 10, Windows Server 2016
> > and Azure. Most of this code was extracted from FreeBSD and some of
> > this is from earlier code donated by Brocade.
> > 
> > Only Linux is supported at present, but the code is split
> > to allow future FreeBSD and Windows support.
> > 
> > This version works with upstream kernel (4.16) but in that
> > mode only a single queue is supported. With additional
> > patches that are pending for 5.0 kernel, multi-queue
> > support works as well.
> > 
> > Device binding is best done via driverctl; this required some
> > additional fixes to kernel and driverctl to work correctly.
> > Linux kernel vmbus support needed to support sysfs driver_override
> > and driverctl needed to handle non-PCI bus from udev.
> >  https://gitlab.com/driverctl/driverctl/merge_requests/3
> >  http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-April/118889.html
> > 
> > v6
> >   - rebase to current 18.05
> >   - fix RSS initialization
> >   - minor documentation fixes
> > 
> > v5
> >   - rebase to current 18.05
> >   - fix message from vmbus due to race on sysfs for sub channel
> > 
> > v4
> >   - don't enable by default because of uuid library dependency
> >   - api's are internal no need to mark experimental
> >   - add netvsc ini file
> >   - fix MAINTAINERS entry
> > 
> > v3
> >   - fix documentation to format correctly and include more info
> >     about binding
> >   - fix build on 32 bit
> >   - minor white space and indentation fixes
> > 
> > Stephen Hemminger (4):
> >   bus/vmbus: add hyper-v virtual bus support
> >   net/netvsc: add hyper-v netvsc network device
> >   net/netvsc: add documentation
> >   bus/vmbus and net/netvsc: add meson build support  
> 
> I confirm my test scripts passes for x86, not able to cross build for other
> architectures because of uuid dependency and I am missing cross version of it.
> note: need to enable both LIBRTE_VMBUS & NETVSC_PMD
> 
> Overall series looks good to me.

Released versions of Hyper-V/Azure are x86 only.
Libuuid should be available for all architectures, for example Debian support x85, arm, mips, ppc, s390

  reply	other threads:[~2018-05-11 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  0:26 Stephen Hemminger
2018-05-09  0:26 ` [dpdk-dev] [PATCH v6 1/4] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-05-09  0:26 ` [dpdk-dev] [PATCH v6 2/4] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-05-09  0:26 ` [dpdk-dev] [PATCH v6 3/4] net/netvsc: add documentation Stephen Hemminger
2018-05-09 15:57   ` Kovacevic, Marko
2018-05-09  0:26 ` [dpdk-dev] [PATCH v4 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-05-11 16:50 ` [dpdk-dev] [PATCH v6 0/4] Hyper-V netvsc PMD and VMBus support Ferruh Yigit
2018-05-11 17:38   ` Stephen Hemminger [this message]
2018-05-12 22:02   ` Thomas Monjalon
2018-05-13 17:22     ` Stephen Hemminger

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=20180511103830.2fc721e5@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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 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).