From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Rami Rosen <ramirose@gmail.com>, Ravi Kerur <rkerur@gmail.com>
Subject: [dpdk-web] [PATCH] trace existing merge l3fwd-acl code into l3fwd work
Date: Mon, 28 Jan 2019 15:06:08 +0000 [thread overview]
Message-ID: <20190128150608.4234-1-ferruh.yigit@intel.com> (raw)
Add the feature into "Nice to have - Future" list with links to latest
patchset and discussion on how to proceed.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Patch is on top of "trace existing eal config file patchset" patch.
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: Rami Rosen <ramirose@gmail.com>
Cc: Ravi Kerur <rkerur@gmail.com>
---
content/roadmap/_index.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index aeb845a..5ae982e 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -29,6 +29,9 @@ This list is obviously neither complete nor guaranteed.
- EAL parameters from config file instead of command-line
- Can benefit from existing patch: https://patches.dpdk.org/patch/26883/
- Discussion: https://mails.dpdk.org/archives/dev/2019-January/123985.html
+- merge l3fwd-acl code into l3fwd
+ - Existing patchset: https://patches.dpdk.org/patch/21696/
+ - Discussion: https://mails.dpdk.org/archives/dev/2019-January/124005.html
### Cycle model {#cycle}
----
--
2.17.2
reply other threads:[~2019-01-28 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190128150608.4234-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ramirose@gmail.com \
--cc=rkerur@gmail.com \
--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).