From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC]Generic flow filtering API Sample Application
Date: Thu, 3 Nov 2016 09:10:48 +0530 [thread overview]
Message-ID: <20161103034047.GA5453@localhost.localdomain> (raw)
In-Reply-To: <A2573D2ACFCADC41BB3BE09C6DE313CA01FE9D0F@PGSMSX103.gar.corp.intel.com>
On Wed, Nov 02, 2016 at 05:27:50AM +0000, Zhao1, Wei wrote:
> Hi All,
> Now we are planning for an sample application for Generic flow
> filtering API feature, and I have finished the RFC for this example app.
> Now Adrien Mazarguil has send v2 version of Generic flow
> filtering API, this sample application RFC is based on that.
>
> Thank you.
>
>
>
>
> Generic flow filtering API Sample Application
> ============================================
>
> The application is a simple example of generic flow filtering API using the DPDK.
> The application performs flow director/filtering/classification in packet processing.
>
> Overview
> --------
>
> The application demonstrates the use of generic flow director/filtering/classification API
> in the DPDK to implement packet forwarding.And this document focus on the guide line of writing rules configuration
> files and prompt commands usage. It also supply the definition of the available EAL options arguments which is useful
> in DPDK packet forwarding processing.
>
>
> Compiling the Application
> -------------------------
>
> To compile the application:
>
> #. Go to the sample application directory:
>
> .. code-block:: console
>
> export RTE_SDK=/path/to/rte_sdk
> cd ${RTE_SDK}/examples/gen_filter
Any specific reason to create a separate application for testing the generic
filter but not as a extension to testpmd?
>
prev parent reply other threads:[~2016-11-03 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 5:27 Zhao1, Wei
2016-11-02 15:47 ` Adrien Mazarguil
2016-11-03 3:40 ` Jerin Jacob [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=20161103034047.GA5453@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=wei.zhao1@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).