From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 67A55A00E6 for ; Tue, 19 Mar 2019 09:38:22 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1FBD51DBD; Tue, 19 Mar 2019 09:38:22 +0100 (CET) Received: from mail-vs1-f52.google.com (mail-vs1-f52.google.com [209.85.217.52]) by dpdk.org (Postfix) with ESMTP id 62B9211A4 for ; Tue, 19 Mar 2019 09:38:20 +0100 (CET) Received: by mail-vs1-f52.google.com with SMTP id b8so11168511vsq.11 for ; Tue, 19 Mar 2019 01:38:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=u5R64WnPLIARc2iPMav+x3hxneSPePtH4zxgrl+ubeA=; b=VmcgRtqnp20gRhTZEKjkF2K1EfZF+KUEi8LYMASO9uy8+CxsSqzZtaU8vM0eYZftC/ GFKqlyHkwZNvyYR3QxSvnBiVsbUu5lkzR5tkC09NNm8bMW24he5JWdGHGZAgFdxON5yT lb6a0Prw3FL4PMUK0UXMdR6mDg7SlV4zX3AjFX3YcfwVmm1nrICt+uHaJAMoFgWj7Db5 8XM8bYrP+tFkhhEqEO/dZaeUgEwbmyr7gA0nCaPDLmZvMCup/S7Qfq5zhoIRoUDIziHK yZxCC2UXRWgN9vhd59DnaLfC0jsukEfILz2TLGKHPdTpd0Lz4hpvbirMIiXB+6gFePjY JDLQ== X-Gm-Message-State: APjAAAXikJxCQ+pFy5Cwzd/gp4m6fAc9ZU9TmO5fN6Kh3eqJz/1Vr0VO D54bawDLs+S7qYuYQPB/Qka0l8GjC+X5pomLxgbQjM2TxKc= X-Google-Smtp-Source: APXvYqwAi0INxo2rck5LPfCyMHFcZdBFo4h7yi+SO0g0YSI9i3ZQLV6ZaAMxnJXNpI5Ebwb6A79jmyT+dsfb5qRPhqA= X-Received: by 2002:a67:c78e:: with SMTP id t14mr612531vsk.180.1552984699521; Tue, 19 Mar 2019 01:38:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Tue, 19 Mar 2019 09:38:08 +0100 Message-ID: To: Jeremy Plsek Cc: ci@dpdk.org Content-Type: multipart/alternative; boundary="0000000000005b679d05846e6dbc" Subject: Re: [dpdk-ci] CI Test Cases X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" --0000000000005b679d05846e6dbc Content-Type: text/plain; charset="UTF-8" Hello Jeremy, On Mon, Mar 18, 2019 at 4:56 PM Jeremy Plsek 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 --0000000000005b679d05846e6dbc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Jeremy,

On Mon, Mar 18, 2019 at = 4:56 PM Jeremy Plsek <jplsek@iol.u= nh.edu> wrote:
Based on last weeks meeting, I've created a document to help star= t
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.

ht= tps://docs.google.com/document/d/1WbRoIq0f5SmHM6D5sLbeh7hxRJdE2ppwB5JECHllL= jg/edit?usp=3Dsharing
(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 pr= efer emails because I did not follow the CI discussions so far and I might = be off topic.

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

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

- No= n regression tests on eth drivers (testpmd seems the best candidate), this = must be ran against a lot of nics/drivers:
=C2=A0 - recepti= on of unicast packets: check that we receive packets for primary and second= ary addresses (and only for them, meaning with checks that undesired packet= s are dropped following updates)
=C2=A0 - promisc support
=C2=A0 - idem with multicast packets
=C2=A0 - link status c= hecks
=C2=A0 - rte_eth_link_up/down checks
=C2=A0 - mtu = checks
=C2=A0 - rss checks
=C2=A0 - ptypes cl= assification
=C2=A0 - stats checks
=C2=A0 - rte= _flow checks
=C2=A0 - port restart checks + associated configurati= on persistency
=C2=A0 - flow control
=C2=A0 - rx/tx = offloads
=C2=A0 - rx/tx descriptor status


--
David Marchand=
--0000000000005b679d05846e6dbc--