DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v10 0/5] Hyper-V/Azure netvsc PMD and bus support
Date: Fri,  8 Jun 2018 09:59:15 -0700	[thread overview]
Message-ID: <20180608165920.12228-1-stephen@networkplumber.org> (raw)

Yet another 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

v10
  - resolve RSS setup 
  - add documentation about restart issue
  - update documentation to refer to 4.17
  - use same RSS key as MLX

v9
  - fix places where still targeted at previous release
  - add map entry for rte_uuid
  - fix meson build dependencies

v8
  - targeted for 18.08, move release notes
  - use Ted's libuuid (not FreeBSD) because that is 3 clause BSD license
    versus 2 clause in FreeBSD
  - minor checkpatch whitespace fixes

v7
  - add EAL UUID functions from BSD to remove dependency on libuuid
    this means device can be enabled by default and eliminates
    build issues
  - add support for latest NetVSP protocol (from hayaingz)
  - add probe finish for compatability with 18.05
  - rebase to 18.05-rc3

             reply	other threads:[~2018-06-08 16:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 16:59 Stephen Hemminger [this message]
2018-06-08 16:59 ` [dpdk-dev] [PATCH v10 1/5] eal: add rte_uuid support Stephen Hemminger
2018-06-08 17:15   ` Wiles, Keith
2018-06-08 18:11     ` Stephen Hemminger
2018-06-10 11:16       ` Jerin Jacob
2018-06-11 17:35         ` Stephen Hemminger
2018-06-08 16:59 ` [dpdk-dev] [PATCH v10 2/5] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-06-08 16:59 ` [dpdk-dev] [PATCH v10 3/5] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-06-08 16:59 ` [dpdk-dev] [PATCH v10 4/5] net/netvsc: add documentation Stephen Hemminger
2018-06-08 16:59 ` [dpdk-dev] [PATCH v10 5/5] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-06-12 15:21 ` [dpdk-dev] [PATCH v10 0/5] Hyper-V/Azure netvsc PMD and bus support Thomas Monjalon
2018-06-12 15:43   ` 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=20180608165920.12228-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@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).