DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/4] Hyper-V Netvsc PMD
Date: Wed, 18 Apr 2018 14:25:45 +0100	[thread overview]
Message-ID: <30f5aec8-3653-28cc-270e-493d7cc53eee@intel.com> (raw)
In-Reply-To: <20180417215324.8576-1-sthemmin@microsoft.com>

On 4/17/2018 10:53 PM, 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
> 
> 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

Overall this is a bus driver implementation and a net driver implementation, it
is not API that effect other part of the DPDK or end user.
As long as it is not breaking anything and documented I am for getting the patch
as experimental for this release.

There are few minor comments on patches.

      parent reply	other threads:[~2018-04-18 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 21:53 Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 1/4] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-04-18 13:16   ` Ferruh Yigit
2018-04-18 16:01     ` Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 2/4] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-04-18 13:19   ` Ferruh Yigit
2018-04-18 16:04     ` Stephen Hemminger
2018-04-18 17:36     ` Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 3/4] net/netvsc: add documentation Stephen Hemminger
2018-04-18 13:25   ` Ferruh Yigit
2018-04-18 16:03     ` Stephen Hemminger
2018-04-18 16:16       ` Ferruh Yigit
2018-04-19 12:37         ` Hemant Agrawal
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-04-18 13:25 ` Ferruh Yigit [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=30f5aec8-3653-28cc-270e-493d7cc53eee@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.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).