From: "Cao, Waterman" <waterman.cao@intel.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Support setting link up and link down
Date: Wed, 4 Jun 2014 15:36:54 +0000 [thread overview]
Message-ID: <AA3F441F262C58498CD6D0C1801DE7EB0AA8CFD2@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1401261302-30140-1-git-send-email-changchun.ouyang@intel.com>
Tested-by: Waterman Cao <waterman.cao at intel.com>
This patch is used to fix bug, and has been tested by Intel.
We verified API by testpmd, it passed.
Please see test steps as the following:
1. In the host machine, set the DPDK environment as usual and start testpmd:
./app/test-pmd/testpmd -c f -n 4 -- -i
2. Start packet forwarding on both ports.
3. In the tester/traffic generator, send the packet with destine MAC to any port on host.
4. Then launch testpmd on host, use the following command to set link up/down to the port:
testpmd> set link-up port 0(or 1)
testpmd> set link-down port 0(or 1)
5. Then check port status
See test environment information as the following:
Fedora 20 x86_64, Linux Kernel 3.13.9-200, GCC 4.8.2
Intel Xeon CPU E5-2680 v2 @ 2.80GHz
NIC: Intel Niantic 82599, Intel i350, Intel 82580 and Intel 82576
next prev parent reply other threads:[~2014-06-04 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 7:14 Ouyang Changchun
2014-05-28 7:15 ` [dpdk-dev] [PATCH v2 1/3] ether: Add API to support set " Ouyang Changchun
2014-05-28 7:15 ` [dpdk-dev] [PATCH v2 2/3] ixgbe: Implement the functionality of setting link up and down in IXGBE PMD Ouyang Changchun
2014-05-28 7:15 ` [dpdk-dev] [PATCH v2 3/3] testpmd: Add commands to test link up and down of PMD Ouyang Changchun
2014-05-28 12:10 ` [dpdk-dev] [PATCH v2 0/3] Support setting link up and link down Ivan Boule
2014-06-11 10:09 ` Thomas Monjalon
2014-06-04 15:36 ` Cao, Waterman [this message]
2014-06-09 16:25 ` Thomas Monjalon
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=AA3F441F262C58498CD6D0C1801DE7EB0AA8CFD2@SHSMSX103.ccr.corp.intel.com \
--to=waterman.cao@intel.com \
--cc=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).