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] [RFC 0/3] Auto enable hotplug with netvsc devices
Date: Thu,  7 May 2020 20:59:03 -0700	[thread overview]
Message-ID: <20200508035906.18359-1-stephen@networkplumber.org> (raw)

In Azure, hotplug is a requirement for a working application.
Yet most applications don't enable it because DPDK hotplug support
is opt-in. 

There are three options:
  1. Blame the application (this seems to be the DPDK default)
  2. Fix the design mistake (too risky at this time)
  3. Automatically enable hotplug if necessary (that is what this
     patchset does).

Stephen Hemminger (3):
  eal/hotplug: allow monitor to be setup by multiple places
  net/vdev_netvsc: automatically enable hotplug support
  net/netvsc: automatically enable hotplug support

 drivers/net/netvsc/hn_ethdev.c        |  5 ++++-
 drivers/net/vdev_netvsc/vdev_netvsc.c |  4 ++++
 lib/librte_eal/linux/eal_dev.c        | 15 +++++++--------
 3 files changed, 15 insertions(+), 9 deletions(-)

-- 
2.20.1


             reply	other threads:[~2020-05-08  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  3:59 Stephen Hemminger [this message]
2020-05-08  3:59 ` [dpdk-dev] [RFC 1/3] eal/hotplug: allow monitor to be setup by multiple places Stephen Hemminger
2020-05-08  3:59 ` [dpdk-dev] [RFC 2/3] net/vdev_netvsc: automatically enable hotplug support Stephen Hemminger
2020-05-08  3:59 ` [dpdk-dev] [RFC 3/3] net/netvsc: " 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=20200508035906.18359-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).