DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH v2 0/4] net/failsafe: support deferred queue start
Date: Thu, 20 Sep 2018 14:55:48 +0100	[thread overview]
Message-ID: <1537451752-28759-1-git-send-email-arybchenko@solarflare.com> (raw)
In-Reply-To: <1535526966-32456-1-git-send-email-arybchenko@solarflare.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="y", Size: 1233 bytes --]

Since the topic is raised in multicast address list patchset, I'd like
to highlight it here as well. Current version uses failsafe ops directly
on sync to synchronize queues state which iterates over all sub-devices.
For already in sync sub-devices it does not go to driver since ethdev
functions checks current state and do nothing if it is already OK.
In theory it is possible to limit it to inactive devices and use
ethdev API instead of direct ops, but it requires a bit more lines of
code.

v2:
    - fix ops ordering
    - update testpmd documentation
    - add Gaëtan's acks

Ian Dolzhansky (4):
  app/testpmd: add queue deferred start switch
  net/failsafe: add checks for deferred queue setup
  net/failsafe: add Rx queue start and stop functions
  net/failsafe: add Tx queue start and stop functions

 app/test-pmd/cmdline.c                      |  91 +++++++++++
 doc/guides/nics/features/failsafe.ini       |   1 +
 doc/guides/rel_notes/release_18_11.rst      |  15 ++
 doc/guides/testpmd_app_ug/testpmd_funcs.rst |   7 +
 drivers/net/failsafe/failsafe_ether.c       |  88 +++++++++++
 drivers/net/failsafe/failsafe_ops.c         | 167 +++++++++++++++++++-
 6 files changed, 368 insertions(+), 1 deletion(-)

-- 
2.17.1

  parent reply	other threads:[~2018-09-20 13:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  7:16 [dpdk-dev] [PATCH " Andrew Rybchenko
2018-08-29  7:16 ` [dpdk-dev] [PATCH 1/4] app/testpmd: add queue deferred start switch Andrew Rybchenko
2018-09-03 16:56   ` Ferruh Yigit
2018-09-20 13:24     ` Andrew Rybchenko
2018-08-29  7:16 ` [dpdk-dev] [PATCH 2/4] net/failsafe: add checks for deferred queue setup Andrew Rybchenko
2018-08-29  7:16 ` [dpdk-dev] [PATCH 3/4] net/failsafe: add Rx queue start and stop functions Andrew Rybchenko
2018-08-29  7:16 ` [dpdk-dev] [PATCH 4/4] net/failsafe: add Tx " Andrew Rybchenko
2018-08-29  9:35 ` [dpdk-dev] [PATCH 0/4] net/failsafe: support deferred queue start Gaëtan Rivet
2018-09-20 13:55 ` Andrew Rybchenko [this message]
2018-09-20 13:55   ` [dpdk-dev] [PATCH v2 1/4] app/testpmd: add queue deferred start switch Andrew Rybchenko
2018-09-20 13:55   ` [dpdk-dev] [PATCH v2 2/4] net/failsafe: add checks for deferred queue setup Andrew Rybchenko
2018-09-20 13:55   ` [dpdk-dev] [PATCH v2 3/4] net/failsafe: add Rx queue start and stop functions Andrew Rybchenko
2018-09-20 13:55   ` [dpdk-dev] [PATCH v2 4/4] net/failsafe: add Tx " Andrew Rybchenko
2018-09-21  0:21   ` [dpdk-dev] [PATCH v2 0/4] net/failsafe: support deferred queue start Ferruh Yigit

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=1537451752-28759-1-git-send-email-arybchenko@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.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).