DPDK CI discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] CI Test Cases
Date: Tue, 19 Mar 2019 09:38:08 +0100	[thread overview]
Message-ID: <CAJFAV8y8-LSh5vniZXR812ckKNa2ELEJVRKRzT53PVu2zO902w@mail.gmail.com> (raw)
In-Reply-To: <CA+xUZB67UM0b2kN=sSPAYBQMOuDisVWx8D7MSKjbP9FmUNE-tA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

Hello Jeremy,

On Mon, Mar 18, 2019 at 4:56 PM Jeremy Plsek <jplsek@iol.unh.edu> wrote:

> Based on last weeks meeting, I've created a document to help start
> documenting what test cases
> should be worked on for cross platform support between NIC vendors and
> which test cases can be used now in the Community Lab.
>
> This list of test cases that should be worked on can be used when
> discussing the budget with the board.
>
> This also gives the Community Lab a list of tests that can be
> implemented in the mean time.
>
>
> https://docs.google.com/document/d/1WbRoIq0f5SmHM6D5sLbeh7hxRJdE2ppwB5JECHllLjg/edit?usp=sharing
> (This document is publicly editable. If I notice the document changes
> outside the scope of the goal, I'll try to revert it and give
> individual access instead.)
>
> If creating this list over email is wanted instead, then we can do it
> in this thread instead of the document. (And I'll update the document
> as emails come in.)
>

Well, for now, I prefer emails because I did not follow the CI discussions
so far and I might be off topic.

Here I go, the list is large, I tried to write from the basic to the most
advanced/less used.

- Non regression tests on basic startup (we can reuse the dpdk ut and/or
enhance them), this part would be hw agnostic:
  - core checks: playing with cpus online/offline + dpdk coremask/list +
checking cpu affinity of all dpdk threads
  - memory checks: a big topic because we have multiple modes at the moment
  - startup devices blacklist/whitelist
  - hotplug (unplug) of devices

- Non regression tests on eth drivers (testpmd seems the best candidate),
this must be ran against a lot of nics/drivers:
  - reception of unicast packets: check that we receive packets for primary
and secondary addresses (and only for them, meaning with checks that
undesired packets are dropped following updates)
  - promisc support
  - idem with multicast packets
  - link status checks
  - rte_eth_link_up/down checks
  - mtu checks
  - rss checks
  - ptypes classification
  - stats checks
  - rte_flow checks
  - port restart checks + associated configuration persistency
  - flow control
  - rx/tx offloads
  - rx/tx descriptor status


-- 
David Marchand

[-- Attachment #2: Type: text/html, Size: 3181 bytes --]

  reply	other threads:[~2019-03-19  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 15:55 Jeremy Plsek
2019-03-19  8:38 ` David Marchand [this message]
2019-04-09 16:44 ` Thomas Monjalon

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=CAJFAV8y8-LSh5vniZXR812ckKNa2ELEJVRKRzT53PVu2zO902w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=ci@dpdk.org \
    --cc=jplsek@iol.unh.edu \
    /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).