From: "Cao, Min" <min.cao@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] examples/vmdq: support new VMDQ API
Date: Thu, 11 Dec 2014 06:01:34 +0000 [thread overview]
Message-ID: <B6059B2012717B4390714544B1F509E110DF05EC@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1415579379-2891-1-git-send-email-huawei.xie@intel.com>
Tested-by: Min Cao <min.cao@intel.com>
Patch name: examples/vmdq: support new VMDQ API
Brief description:
Test Flag: Tested-by
Tester name: min.cao@intel.com
Result summary: total 1 cases, 1 passed, 0 failed
Test Case 1:
Name: perf_vmdq_performance
Environment: OS: Fedora20 3.11.10-301.fc20.x86_64
gcc (GCC) 4.8.2
CPU: Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
NIC: Fortville eagle
Test result: PASSED
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Huawei Xie
Sent: Monday, November 10, 2014 8:30 AM
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/2] examples/vmdq: support new VMDQ API
This patch supports new VMDQ API in vmdq example.
v2 changes:
* code rebase
* allow app to specify num_pools different with max_nb_pools
* fix serious cs issues
Huawei Xie (2):
support new VMDQ API in vmdq example
fix cs issues in vmdq example
examples/vmdq/main.c | 233 ++++++++++++++++++++++++++++++---------------------
1 file changed, 139 insertions(+), 94 deletions(-)
--
1.8.1.4
prev parent reply other threads:[~2014-12-11 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 0:29 Huawei Xie
2014-11-10 0:29 ` [dpdk-dev] [PATCH v2 1/2] " Huawei Xie
2014-11-10 0:29 ` [dpdk-dev] [PATCH v2 2/2] examples/vmdq: fix cs issues in vmdq example Huawei Xie
2014-11-10 3:41 ` [dpdk-dev] [PATCH v2 0/2] examples/vmdq: support new VMDQ API Chen, Jing D
2014-11-11 22:49 ` Thomas Monjalon
2014-12-11 6:01 ` Cao, Min [this message]
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=B6059B2012717B4390714544B1F509E110DF05EC@SHSMSX103.ccr.corp.intel.com \
--to=min.cao@intel.com \
--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).