From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] ip_pipeline: add sample configuration/script files
Date: Mon, 14 Dec 2015 14:28:33 +0100 [thread overview]
Message-ID: <2746388.sSZjSxRLON@xps13> (raw)
In-Reply-To: <1450097325-86556-1-git-send-email-jasvinder.singh@intel.com>
2015-12-14 12:48, Jasvinder Singh:
> This patch includes the configuration and script
> files of the some applications which can
> be built using DPDK Packet Framework. A
> configuration file defines the application
> structure which include packet processing stages
> (knowns as pipelines), their connectivity and
> other parameters necessary to start and run the
> application. A script file specifies CLI commands
> required for loading table entries (rules/routes,
> etc). The configuration/script files for simple
> applications such as l2 forwarding, l3 forwarding
> have been presented. In addition, to demonstrate
> the use and inter-connectivity of various pipeline
> modules (which are avilable in packet framework),
> a complex packet processing workload i.e. edge
> router is considered. The configuration of the
> pipeline stages used for upstream and downstream
> flow processing has been specified separately in
> two configuration files. All these configuration
> and script files don't affect the compilation.
Please use at least 70 chars-wide lines.
It would also be easier to read with some paragraphs.
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> *v2
> - correct date in license header(edge_router_downstream/upstream.cfg)
> - modify commit message
>
> *v3
> - correct date in license header(l2fwd.cfg, l3fwd.cfg)
>
> .../ip_pipeline/config/edge_router_downstream.cfg | 85 ++++++++++++++++
> .../ip_pipeline/config/edge_router_downstream.sh | 10 ++
> .../ip_pipeline/config/edge_router_upstream.cfg | 110 +++++++++++++++++++++
> .../ip_pipeline/config/edge_router_upstream.sh | 38 +++++++
> examples/ip_pipeline/config/l2fwd.cfg | 55 +++++++++++
> examples/ip_pipeline/config/l3fwd.cfg | 63 ++++++++++++
> examples/ip_pipeline/config/l3fwd.sh | 9 ++
> 7 files changed, 370 insertions(+)
> create mode 100755 examples/ip_pipeline/config/edge_router_downstream.cfg
> create mode 100755 examples/ip_pipeline/config/edge_router_downstream.sh
> create mode 100755 examples/ip_pipeline/config/edge_router_upstream.cfg
> create mode 100755 examples/ip_pipeline/config/edge_router_upstream.sh
> create mode 100755 examples/ip_pipeline/config/l2fwd.cfg
> create mode 100755 examples/ip_pipeline/config/l3fwd.cfg
> create mode 100755 examples/ip_pipeline/config/l3fwd.sh
checkpatch says:
EXECUTE_PERMISSIONS: do not set execute permissions for source files
next prev parent reply other threads:[~2015-12-14 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 21:28 [PATCH] ip_pipeline: add sample configuration/script files Jasvinder Singh
2015-12-14 12:12 ` [PATCH v2] " Jasvinder Singh
2015-12-14 12:48 ` [PATCH v3] " Jasvinder Singh
2015-12-14 13:28 ` Thomas Monjalon [this message]
2015-12-14 14:20 ` [PATCH v4] " Jasvinder Singh
2015-12-14 21:55 ` 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=2746388.sSZjSxRLON@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.