Netdev List
 help / color / mirror / Atom feed
From: Roman Mashak <mrv@mojatatu.com>
To: Davide Caratti <dcaratti@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	"Brenda J . Butler" <bjb@mojatatu.com>
Subject: Re: [PATCH net-next] tc-testing: add selftests for 'bpf' action
Date: Mon, 19 Mar 2018 14:40:18 -0400	[thread overview]
Message-ID: <85po3zgb8t.fsf@mojatatu.com> (raw)
In-Reply-To: <14be6cc1ace745b6ee37e552bc0e317e7ae765ec.1521418521.git.dcaratti@redhat.com> (Davide Caratti's message of "Mon, 19 Mar 2018 01:19:08 +0100")

Davide Caratti <dcaratti@redhat.com> writes:

> Test d959: Add cBPF action with valid bytecode
> Test f84a: Add cBPF action with invalid bytecode
> Test e939: Add eBPF action with valid object-file
> Test d819: Replace cBPF bytecode and action control
> Test 6ae3: Delete cBPF action
> Test 3e0d: List cBPF actions
> Test 55ce: Flush BPF actions
> Test ccc3: Add cBPF action with duplicate index
>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
> ---
>  .../selftests/tc-testing/tc-tests/actions/bpf.json | 215 +++++++++++++++++++++
>  1 file changed, 215 insertions(+)
>  create mode 100644 tools/testing/selftests/tc-testing/tc-tests/actions/bpf.json
>
> diff --git a/tools/testing/selftests/tc-testing/tc-tests/actions/bpf.json b/tools/testing/selftests/tc-testing/tc-tests/actions/bpf.json
> new file mode 100644
> index 000000000000..0295a63dd0c8

[...]

Davide, thank you for efforts. Please also add a test for testing max
index value (since it is u32 type) and a test with cookie (every action
may have optional 128-bit value, that carries some user state and not
intepreted by the kernel).

      reply	other threads:[~2018-03-19 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19  0:19 [PATCH net-next] tc-testing: add selftests for 'bpf' action Davide Caratti
2018-03-19 18:40 ` Roman Mashak [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=85po3zgb8t.fsf@mojatatu.com \
    --to=mrv@mojatatu.com \
    --cc=bjb@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=netdev@vger.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