From: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
To: dev@dpdk.org
Cc: kirill.rybalchenko@intel.com, andrey.chilikin@intel.com,
beilei.xing@intel.com, jingjing.wu@intel.com
Subject: [PATCH v6 0/2] net/i40e: get information about protocols defined in ddp profile
Date: Thu, 28 Sep 2017 14:33:17 +0100 [thread overview]
Message-ID: <1506605599-31693-1-git-send-email-kirill.rybalchenko@intel.com> (raw)
In-Reply-To: <1505843612-40976-1-git-send-email-kirill.rybalchenko@intel.com>
This patch adds ability to request information about protocols defined in dynamic
device personalization profile
v2:
Some code style warnings were removed
v3:
info_size parameter always represents size of the info buffer in bytes;
fix code style;
v4:
another code style fixes
v5:
in testpmd buff_size parameter in rte_pmd_i40e_get_ddp_info function call
always represents buffer size in bytes
v6:
fix bug with wrong usage of buff_size parameter
Kirill Rybalchenko (2):
net/i40e: get information about protocols defined in ddp profile
app/testpmd: get information about protocols defined in ddp profile
app/test-pmd/cmdline.c | 120 +++++++++++++++++++++++++--
drivers/net/i40e/rte_pmd_i40e.c | 174 ++++++++++++++++++++++++++++++++++++++++
drivers/net/i40e/rte_pmd_i40e.h | 25 ++++++
3 files changed, 312 insertions(+), 7 deletions(-)
--
2.5.5
next prev parent reply other threads:[~2017-09-28 13:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4075836-102681-1-git-send-email-kirill.rybalchenko@intel.com>
2017-09-01 16:01 ` [PATCH v2 0/2] net/i40e: get information about protocols defined in ddp profile Kirill Rybalchenko
2017-09-01 16:01 ` [PATCH v2 1/2] " Kirill Rybalchenko
2017-09-04 12:36 ` Iremonger, Bernard
2017-09-11 15:32 ` Ferruh Yigit
2017-09-01 16:01 ` [PATCH v2 2/2] app/testpmd: " Kirill Rybalchenko
2017-09-04 12:44 ` Iremonger, Bernard
2017-09-04 12:46 ` Iremonger, Bernard
2017-09-11 15:32 ` Ferruh Yigit
2017-09-19 16:46 ` [PATCH v3 0/2] net/i40e: " Kirill Rybalchenko
2017-09-19 16:46 ` [PATCH v3 1/2] " Kirill Rybalchenko
2017-09-19 16:46 ` [PATCH v3 2/2] app/testpmd: " Kirill Rybalchenko
2017-09-19 17:32 ` [PATCH v4 0/2] net/i40e: " Kirill Rybalchenko
2017-09-19 17:32 ` [PATCH v4 1/2] " Kirill Rybalchenko
2017-09-19 17:32 ` [PATCH v4 2/2] app/testpmd: " Kirill Rybalchenko
2017-09-19 17:53 ` [PATCH v5 0/2] net/i40e: " Kirill Rybalchenko
2017-09-19 17:53 ` [PATCH v5 1/2] " Kirill Rybalchenko
2017-09-26 3:35 ` Xing, Beilei
2017-09-19 17:53 ` [PATCH v5 2/2] app/testpmd: " Kirill Rybalchenko
2017-09-28 13:33 ` Kirill Rybalchenko [this message]
2017-09-28 13:33 ` [PATCH v6 1/2] net/i40e: " Kirill Rybalchenko
2017-09-29 7:30 ` Xing, Beilei
2017-09-28 13:33 ` [PATCH v6 2/2] app/testpmd: " Kirill Rybalchenko
2017-10-02 9:39 ` [PATCH v7 0/2] net/i40e: " Kirill Rybalchenko
2017-10-02 9:39 ` [PATCH v7 1/2] " Kirill Rybalchenko
2017-10-02 9:39 ` [PATCH v7 2/2] app/testpmd: " Kirill Rybalchenko
2017-10-04 14:00 ` [PATCH v8 0/2] et/i40e: " Kirill Rybalchenko
2017-10-04 14:00 ` [PATCH v8 1/2] net/i40e: " Kirill Rybalchenko
2017-10-04 14:00 ` [PATCH v8 2/2] app/testpmd: " Kirill Rybalchenko
2017-10-04 22:00 ` [PATCH v8 0/2] et/i40e: " Ferruh Yigit
2017-10-05 1:11 ` Ferruh Yigit
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=1506605599-31693-1-git-send-email-kirill.rybalchenko@intel.com \
--to=kirill.rybalchenko@intel.com \
--cc=andrey.chilikin@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.