DPDK patches and discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dev@dpdk.org
Subject: [dpdk-dev] Fwd: Request for High Priority Features
Date: Tue, 28 Jul 2020 13:35:13 -0400	[thread overview]
Message-ID: <CAHx6DYBXkAKqtAZGf3H6QodqM596UhHbwq0c-UjkG5=bjpK0pg@mail.gmail.com> (raw)
In-Reply-To: <CAHx6DYB=qaxb+kGs6yu_+ZQ3Q1efyOuCvD-EJRTJbfU5L7mSDQ@mail.gmail.com>

---------- Forwarded message ---------
From: Owen Hilyard <ohilyard@iol.unh.edu>
Date: Tue, Jul 28, 2020 at 8:04 AM
Subject: Request for High Priority Features
To: <dts@dpdk.org>


Hello Everyone,

Those of us at the IOL have been working on new DTS test cases for a while
now, and we are starting to get to the point where we've completed most of
the simpler test cases we are aware of. The remaining features are ones we
have internally agreed are either not supported by most NICS (Table 1.1
<http://doc.dpdk.org/guides/nics/overview.html>) or are features that we
think will require a large time investment to complete. This large time
investment may be due to the complexity required of a test which properly
checks different scenarios, a lack of knowledge about specific parts of the
spec we are testing against, or a lack of support in dpdk for the feature.
We don't want to spend a large amount of time focusing on a feature which
isn't important, and as such we are requesting that the community send us a
list of high priority features. We don't need a consensus before these are
sent to us, since we can look at multiple people's lists and find the
important ones from the aggregate.

The current state of our development progress can be found in the attached
google sheet.
 DPDK Test Cases Status List
<https://docs.google.com/spreadsheets/d/1xeGQZdt6R3FrxMUSfbLRMKObDs7yGEODuXSLw4OjSco/edit?usp=drive_web>


Thanks for your assistance,
The IOL Team

           reply	other threads:[~2020-07-28 17:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAHx6DYB=qaxb+kGs6yu_+ZQ3Q1efyOuCvD-EJRTJbfU5L7mSDQ@mail.gmail.com>]

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='CAHx6DYBXkAKqtAZGf3H6QodqM596UhHbwq0c-UjkG5=bjpK0pg@mail.gmail.com' \
    --to=ohilyard@iol.unh.edu \
    --cc=dev@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).