From: "Cao, Waterman" <waterman.cao@intel.com>
To: "Liu, Jijiang" <jijiang.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] *** Upgrade NIC share codes ***
Date: Wed, 4 Jun 2014 14:53:09 +0000 [thread overview]
Message-ID: <AA3F441F262C58498CD6D0C1801DE7EB0AA8CECA@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1400120294-15871-1-git-send-email-jijiang.liu@intel.com>
Tested-by: Waterman Cao <waterman.cao@intel.com>
Totally this patch is composed of 4 files including cover letter, and has been tested by Intel.
We verified latest NIC share code with different kind of NICs, please see the list as the followings:
Type Product Name
1G Powerville (Intel Ethernet Controller I350 - T4)
1G Springville(Intel Ethernet Controller I210 1x1000BASE-T)
1G Intel 82576 1G 1000BASE-T
10G Intel 82599 10Gb Ethernet Controller - X520 - SR2
10G Intel 82599 10Gb Ethernet Controller - X520 - T2
10G Intel 82599 10Gb Ethernet Controller 4 x 10GbE - SFP+
10G Intel Ethernet Controller X540 2x10GBASE-T
All basic NIC function test are passed with latest NIC share code, including PMD, Flow Direction, L2 FWD, Dual vlan, ip reassembly, etc.
Test environment: Fedora 20, Linux Kernel 3.12.11, GCC 4.8.2, Intel Xeon processor E5-2680 v2.
next prev parent reply other threads:[~2014-06-04 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 2:18 Jijiang Liu
2014-05-15 2:18 ` [dpdk-dev] [PATCH 1/3] Upgrade share codes:upgrade NIC shared code in ixgbe & e1000 directories Jijiang Liu
2014-05-15 2:18 ` [dpdk-dev] [PATCH 2/3] Upgrade share codes:fix an issue of hash calculation of flow director introduced by upgrading NIC share codes Jijiang Liu
2014-05-15 2:18 ` [dpdk-dev] [PATCH 3/3] Upgrade share codes:change Copyright date of e1000_osdep.c and e1000_osdep.h files Jijiang Liu
2014-05-19 9:18 ` [dpdk-dev] [PATCH 0/3] *** Upgrade NIC share codes *** Thomas Monjalon
2014-05-27 1:51 ` Liu, Jijiang
2014-06-18 21:51 ` Thomas Monjalon
2014-06-04 14:53 ` Cao, Waterman [this message]
2014-06-05 5:20 ` Zhang, Helin
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=AA3F441F262C58498CD6D0C1801DE7EB0AA8CECA@SHSMSX103.ccr.corp.intel.com \
--to=waterman.cao@intel.com \
--cc=dev@dpdk.org \
--cc=jijiang.liu@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).