netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Buslov <vladbu@mellanox.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jhs@mojatatu.com, lucasb@mojatatu.com,
	mrv@mojatatu.com, shuah@kernel.org,
	batuhanosmantaskaya@gmail.com, dcaratti@redhat.com,
	marcelo.leitner@gmail.com, Vlad Buslov <vladbu@mellanox.com>
Subject: [PATCH net-next 0/2] Fix problems with using ns plugin
Date: Mon, 19 Aug 2019 10:52:06 +0300	[thread overview]
Message-ID: <20190819075208.12240-1-vladbu@mellanox.com> (raw)

Recent changes to plugin architecture broke some of the tests when running tdc
without specifying a test group. Fix tests incompatible with ns plugin and
modify tests to not reuse interface name of ns veth interface for dummy
interface.

Vlad Buslov (2):
  tc-testing: use dedicated DUMMY interface name for dummy dev
  tc-testing: concurrency: wrap piped rule update commands

 .../tc-tests/filters/concurrency.json         |  18 +-
 .../tc-testing/tc-tests/filters/matchall.json | 242 +++++++++---------
 .../tc-testing/tc-tests/qdiscs/fifo.json      | 150 +++++------
 .../tc-testing/tc-tests/qdiscs/ingress.json   |  50 ++--
 .../tc-testing/tc-tests/qdiscs/prio.json      | 128 ++++-----
 .../selftests/tc-testing/tdc_config.py        |   1 +
 6 files changed, 295 insertions(+), 294 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-08-19  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  7:52 Vlad Buslov [this message]
2019-08-19  7:52 ` [PATCH net-next 1/2] tc-testing: use dedicated DUMMY interface name for dummy dev Vlad Buslov
2019-08-19  7:52 ` [PATCH net-next 2/2] tc-testing: concurrency: wrap piped rule update commands Vlad Buslov
2019-08-20  1:20 ` [PATCH net-next 0/2] Fix problems with using ns plugin David Miller

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=20190819075208.12240-1-vladbu@mellanox.com \
    --to=vladbu@mellanox.com \
    --cc=batuhanosmantaskaya@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=lucasb@mojatatu.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=mrv@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.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).