[dpdk-dev] [PATCH v3] ip_pipeline: add sample configuration/script files
Thomas Monjalon
thomas.monjalon at 6wind.com
Mon Dec 14 14:28:33 CET 2015
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 at intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu at 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
More information about the dev
mailing list