Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: lucasb@mojatatu.com
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, jiri@resnulli.us, mleitner@redhat.com,
	vladbu@mellanox.com, dcaratti@redhat.com, kernel@mojatatu.com
Subject: Re: [PATCH net-next 0/2] tc-testing: Add plugin for simple traffic generation
Date: Tue, 09 Jul 2019 14:08:00 -0700 (PDT)	[thread overview]
Message-ID: <20190709.140800.430247967116331219.davem@davemloft.net> (raw)
In-Reply-To: <1562636067-1338-1-git-send-email-lucasb@mojatatu.com>

From: Lucas Bates <lucasb@mojatatu.com>
Date: Mon,  8 Jul 2019 21:34:25 -0400

> This series supersedes the previous submission that included a patch for test
> case verification using JSON output.  It adds a new tdc plugin, scapyPlugin, as
> a way to send traffic to test tc filters and actions.
> 
> The first patch makes a change to the TdcPlugin module that will allow tdc
> plugins to examine the test case currently being executed, so plugins can
> play a more active role in testing by accepting information or commands from
> the test case.  This is required for scapyPlugin to work.
> 
> The second patch adds scapyPlugin itself, and an example test case file to
> demonstrate how the scapy block works in the test cases.

So I'm going to apply this series for now, and I encourage you folks
to continue eval() and python knowledge discussion further.

Thanks.

      parent reply	other threads:[~2019-07-09 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09  1:34 [PATCH net-next 0/2] tc-testing: Add plugin for simple traffic generation Lucas Bates
2019-07-09  1:34 ` [PATCH net-next 1/2] tc-testing: Allow tdc plugins to see test case data Lucas Bates
2019-07-09  1:34 ` [PATCH net-next 2/2] tc-testing: introduce scapyPlugin for basic traffic Lucas Bates
2019-07-09 11:44 ` [PATCH net-next 0/2] tc-testing: Add plugin for simple traffic generation Jamal Hadi Salim
2019-07-09 21:08 ` David Miller [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=20190709.140800.430247967116331219.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel@mojatatu.com \
    --cc=lucasb@mojatatu.com \
    --cc=mleitner@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@mellanox.com \
    --cc=xiyou.wangcong@gmail.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