From: Olivier MATZ <olivier.matz@6wind.com>
To: "Cao, Min" <min.cao@intel.com>,
"Liu, Jijiang" <jijiang.liu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] Support NVGRE on i40e
Date: Wed, 28 Jan 2015 12:08:12 +0100 [thread overview]
Message-ID: <54C8C31C.5020007@6wind.com> (raw)
In-Reply-To: <B6059B2012717B4390714544B1F509E110E14555@SHSMSX103.ccr.corp.intel.com>
Hi Min,
On 01/27/2015 06:46 AM, Cao, Min wrote:
> Test by: min.cao <min.cao@intel.com>
> Patch name: [dpdk-dev] [PATCH 0/6] Support NVGRE on i40e
> Test Flag: Tested-by
> Tester name: min.cao@intel.com
> Result summary: total 2 cases, 2 passed, 0 failed
>
> Test Case 1:
> Name: nvgre filter
> 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
> [...]
Just one remarq about your test report: it's quite useful to have
such reports, showing that a feature is tested. However, I think
it would be much better if you provide all the means to reproduce
the test (testpmd configuration, scripts to generate packets, ...).
For instance, this could help people wanting to implement the same
on another PMD to validate with the same test plan than yours.
Regards,
Olivier
prev parent reply other threads:[~2015-01-28 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 3:43 Jijiang Liu
2015-01-26 3:43 ` [dpdk-dev] [PATCH 1/6] librte_ether:add NVGRE header Jijiang Liu
2015-01-26 3:43 ` [dpdk-dev] [PATCH 2/6] i40e:support RX tunnel filter for NVGRE packet Jijiang Liu
2015-01-26 3:43 ` [dpdk-dev] [PATCH 3/6] app/testpmd:test " Jijiang Liu
2015-01-26 3:43 ` [dpdk-dev] [PATCH 4/6] mbuf:add a GRE TX tunnel ol_flag Jijiang Liu
2015-01-26 3:43 ` [dpdk-dev] [PATCH 5/6] i40e:support GRE tunnel TX checksum offload Jijiang Liu
2015-01-26 3:43 ` [dpdk-dev] [PATCH 6/6] app/testpmd:test NVGRE Tx " Jijiang Liu
2015-01-27 5:46 ` [dpdk-dev] [PATCH 0/6] Support NVGRE on i40e Cao, Min
2015-01-28 11:08 ` Olivier MATZ [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=54C8C31C.5020007@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=jijiang.liu@intel.com \
--cc=min.cao@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 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).