From: "Graham, Debra H" <debra.h.graham@intel.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: [dpdk-users] Contributor article: Introduction to the Data Plane Development Kit (DPDK) Packet Framework by Jasvinder Singh
Date: Fri, 10 Mar 2017 16:24:26 +0000 [thread overview]
Message-ID: <0EACE147D735F447B04F7323CBC3B3CB19B55411@ORSMSX107.amr.corp.intel.com> (raw)
Hi,
I'm Debbie Graham from the Intel Developer Zone (IDZ). We publish articles by Intel DPDK developers and other experts about DPDK features, testing, and performance. This article, Introduction to the Data Plane Development Kit (DPDK) Packet Framework<https://software.intel.com/en-us/articles/introduction-to-the-data-plane-development-kit-dpdk-packet-framework> by Jasvinder Singh, was just published and focuses on the ip_pipeline.
We're interested in your feedback, and if there is other content you'd like to see from IDZ, please let me know.
Best regards,
Debbie
reply other threads:[~2017-03-10 16:24 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=0EACE147D735F447B04F7323CBC3B3CB19B55411@ORSMSX107.amr.corp.intel.com \
--to=debra.h.graham@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=john.mcnamara@intel.com \
--cc=users@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).