From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: web@dpdk.org, thomas@monjalon.net, ferruh.yigit@intel.com,
stephen@networkplumber.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-web] [PATCH] Add section in roadmap for internship topics
Date: Fri, 8 Feb 2019 10:18:07 +0100 [thread overview]
Message-ID: <20190208091807.1569-1-maxime.coquelin@redhat.com> (raw)
The patch also adds two topics I have in mind:
- Vhost & Virtio testing
- Monitor socket for testpmd
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
---
content/roadmap/_index.md | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 281002c..852e476 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -27,6 +27,22 @@ This list is obviously neither complete nor guaranteed.
- generic white/blacklisting
- libedit integration
+### Internship topic ideas
+----
+- Vhost & Virtio functionnal testing in DPDK CI
+ - Mentor: Maxime Coquelin <maxime.coquelin@redhat.com>
+ - Languages: C, Python, Bash
+ - The goal is to develop and integrate testing of Virtio and Vhost
+ in DPDK CI.
+- Monitor socket implementation in testpmd to ease CI integration
+ - Mentor: TBD
+ - Languages: C, Python
+ - Instead on controlling and querying testpmd over stdin/stdout,
+ the idea is to have a dedicated socket for that. A protocol would
+ have to be defined, and could e.g. use JSON format so that it is
+ human-readable. It could be also extended to be able to register
+ to asynchronous events like packets drop notification.
+
### Cycle model {#cycle}
----
A typical release should be done after 3 months.
--
2.20.1
next reply other threads:[~2019-02-08 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 9:18 Maxime Coquelin [this message]
2019-02-13 20:24 ` 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=20190208091807.1569-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=web@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).