From: "Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/11] ip_pipeline: ip_pipeline application enhancements
Date: Tue, 23 Jun 2015 13:54:18 +0000 [thread overview]
Message-ID: <9CC680510C0AC140A846FED2EF7F962813846DE1@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1989026.g49HqGv7mc@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, June 23, 2015 3:49 PM
> To: Gajdzica, MaciejX T
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 00/11] ip_pipeline: ip_pipeline application
> enhancements
>
> Is this patchset still candidate for 2.1?
Yes, it is, but some changes need to be made. V2 will be send in a few days.
Best Regards
Maciek
>
> 2015-05-29 17:43, Maciej Gajdzica:
> > This patchset enhances functionality of ip_pipeline application. New
> > config file syntax is introduced, so parser is changed. Changed
> > structure of the application. Now every global variable is stored in app_struct
> in app.h.
> > Syntax of pipeline cli commands was changed. Implementation of cli
> > commands for every pipeline is moved to the separate file.
> >
> >
> > Maciej Gajdzica (11):
> > ip_pipeline: add parsing for config files with new syntax
> > ip_pipeline: added config checks
> > ip_pipeline: modified init to match new params struct
> > ip_pipeline: moved pipelines to separate folder
> > ip_pipeline: added master pipeline
> > ip_pipeline: added application thread
> > ip_pipeline: moved config files to separate folder
> > ip_pipeline: added new implementation of passthrough pipeline
> > ip_pipeline: added new implementation of firewall pipeline
> > ip_pipeline: added new implementation of routing pipeline
> > ip_pipeline: added new implementation of flow classification
> > pipeline
>
prev parent reply other threads:[~2015-06-23 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 15:43 Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 01/11] ip_pipeline: add parsing for config files with new syntax Maciej Gajdzica
2015-06-01 13:34 ` Stephen Hemminger
2015-06-04 17:29 ` Dumitrescu, Cristian
2015-05-29 15:43 ` [dpdk-dev] [PATCH 02/11] ip_pipeline: added config checks Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 03/11] ip_pipeline: modified init to match new params struct Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 04/11] ip_pipeline: moved pipelines to separate folder Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 05/11] ip_pipeline: added master pipeline Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 06/11] ip_pipeline: added application thread Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 07/11] ip_pipeline: moved config files to separate folder Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 08/11] ip_pipeline: added new implementation of passthrough pipeline Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 09/11] ip_pipeline: added new implementation of firewall pipeline Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 10/11] ip_pipeline: added new implementation of routing pipeline Maciej Gajdzica
2015-05-29 15:43 ` [dpdk-dev] [PATCH 11/11] ip_pipeline: added new implementation of flow classification pipeline Maciej Gajdzica
2015-06-23 13:48 ` [dpdk-dev] [PATCH 00/11] ip_pipeline: ip_pipeline application enhancements Thomas Monjalon
2015-06-23 13:54 ` Gajdzica, MaciejX T [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=9CC680510C0AC140A846FED2EF7F962813846DE1@IRSMSX102.ger.corp.intel.com \
--to=maciejx.t.gajdzica@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).