From: "Liu, Yong" <yong.liu@intel.com>
To: "Xu, GangX" <gangx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, GangX" <gangx.xu@intel.com>
Subject: Re: [dts] [PATCH V3] add rxtx_callbacks test plan code
Date: Wed, 4 May 2016 17:06:17 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E14F1B100@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1462330876-3890-5-git-send-email-gangx.xu@intel.com>
Applied. Thanks.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,gang
> Sent: Tuesday, May 03, 2016 8:01 PM
> To: dts@dpdk.org
> Cc: Xu, GangX
> Subject: [dts] [PATCH V3] add rxtx_callbacks test plan code
>
> Signed-off-by: xu,gang <gangx.xu@intel.com>
> ---
> test_plans/rxtx_callbacks_test_plan.rst | 68
> +++++++++++++++++++++++++++++++++
> 1 file changed, 68 insertions(+)
> create mode 100644 test_plans/rxtx_callbacks_test_plan.rst
>
> diff --git a/test_plans/rxtx_callbacks_test_plan.rst
> b/test_plans/rxtx_callbacks_test_plan.rst
> new file mode 100644
> index 0000000..e954789
> --- /dev/null
> +++ b/test_plans/rxtx_callbacks_test_plan.rst
> @@ -0,0 +1,68 @@
> +.. BSD LICENSE
> + Copyright(c) 2016 Intel Corporation. All rights reserved.
> + All rights reserved.
> +
> + Redistribution and use in source and binary forms, with or without
> + modification, are permitted provided that the following conditions
> + are met:
> +
> + * Redistributions of source code must retain the above copyright
> + notice, this list of conditions and the following disclaimer.
> + * Redistributions in binary form must reproduce the above copyright
> + notice, this list of conditions and the following disclaimer in
> + the documentation and/or other materials provided with the
> + distribution.
> + * Neither the name of Intel Corporation nor the names of its
> + contributors may be used to endorse or promote products derived
> + from this software without specific prior written permission.
> +
> + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> + A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
> + OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> + LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> + DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
> + THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> + OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +
> +RX/TX Callbacks Sample Application
> +==================================
> +
> +The RX/TX Callbacks sample application is a packet forwarding application
> that
> +demonstrates the use of user defined callbacks on received and
> transmitted
> +packets. The application performs a simple latency check, using callbacks,
> to
> +determine the time packets spend within the application.
> +
> +In the sample application a user defined callback is applied to all
> received
> +packets to add a timestamp. A separate callback is applied to all packets
> +prior to transmission to calculate the elapsed time, in CPU cycles.
> +
> +Running the Application
> +-----------------------
> +open common_base CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y
> +To run the example in a ``linuxapp`` environment:
> +
> + ./build/rxtx_callbacks -c 2 -n 4
> +
> +Refer to *DPDK Getting Started Guide* for general information on running
> +applications and the Environment Abstraction Layer (EAL) options.
> +
> +test_rxtx_callbacks
> +===================
> +
> +Runing::
> + ./examples/rxtx_callbacks/build/rxtx_callbacks -c 2 -n 4
> +
> +waked up :
> + Core X forwarding packets.
> +
> +Send one packet on Port0,check the port1 receive packet.
> +It receive one packet that the port0 send.
> +
> +
> +
> +
> --
> 1.9.3
next prev parent reply other threads:[~2016-05-04 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 3:01 [dts] [PATCH V3] add Test netmap_compat code xu,gang
2016-05-04 3:01 ` [dts] [PATCH V3] add Test rxtx_callbacks code xu,gang
2016-05-04 3:01 ` [dts] [PATCH V3] add TestSuite skeleton code xu,gang
2016-05-04 16:59 ` Liu, Yong
2016-05-04 3:01 ` [dts] [PATCH V3] add netmap_compat test plan code xu,gang
2016-05-04 3:01 ` [dts] [PATCH V3] add rxtx_callbacks " xu,gang
2016-05-04 17:06 ` Liu, Yong [this message]
2016-05-04 3:01 ` [dts] [PATCH V3] add skeleton " xu,gang
2016-05-04 16:57 ` Liu, Yong
2016-05-04 17:02 ` [dts] [PATCH V3] add Test netmap_compat code Liu, Yong
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=86228AFD5BCD8E4EBFD2B90117B5E81E14F1B100@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=gangx.xu@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).