From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 407] Add ether layer testing to the community lab
Date: Tue, 25 Feb 2020 16:32:36 +0000 [thread overview]
Message-ID: <bug-407-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=407
Bug ID: 407
Summary: Add ether layer testing to the community lab
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: UNH infra
Assignee: ci@dpdk.org
Reporter: jplsek@iol.unh.edu
CC: jplsek@iol.unh.edu
Target Milestone: ---
From: http://mails.dpdk.org/archives/ci/2019-March/000375.html
promisc support
idem with multicast packets
link status checks
rte_eth_link_up/down checks
mtu checks: test various common sizes, larger sizes (1500+), error sizes
rss checks
ptypes classification
stats checks
rte_flow checks
port restart checks + associated configuration persistency
flow control
rx/tx offloads
rx/tx descriptor status
This seems to involve creating new tests, which UNH-IOL will try to look into.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-02-25 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 16:32 bugzilla [this message]
2020-04-21 14:17 ` bugzilla
2020-04-21 14:20 ` bugzilla
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=bug-407-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@dpdk.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).