DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6 05/11] ip_pipeline: added master pipeline
Date: Thu, 9 Jul 2015 08:03:25 +0000	[thread overview]
Message-ID: <9CC680510C0AC140A846FED2EF7F96281384BCDC@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <2556845.B31QGe61c9@xps13>

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, July 09, 2015 12:33 AM
> To: Gajdzica, MaciejX T; Singh, Jasvinder
> Cc: dev@dpdk.org; Dumitrescu, Cristian
> Subject: Re: [dpdk-dev] [PATCH v6 05/11] ip_pipeline: added master pipeline
> 
> 2015-07-07 10:09, Maciej Gajdzica:
> > From: Jasvinder Singh <jasvinder.singh@intel.com>
> >
> > Master pipeline is responsible for command line handling and
> > communicationg with all other pipelines via message queues. Removed
> > cmdline.c file, as its functionality will be split over multiple
> > pipeline files.
> >
> > Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> 
> In this v6, it builds well until patch 05 which uses some not exported symbols:
> pipeline_common_be.c:(.text+0x51): undefined reference to
> `rte_pipeline_port_in_stats_read'
> pipeline_common_be.c:(.text+0x91): undefined reference to
> `rte_pipeline_port_out_stats_read'
> pipeline_common_be.c:(.text+0xd4): undefined reference to
> `rte_pipeline_table_stats_read'
> 
> Please check build with shared libraries.

There are missing symbols in map file for librte_port and librte_pipeline. I will send separate patch for that.

Best Regards
Maciek

  reply	other threads:[~2015-07-09  8:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  8:09 [dpdk-dev] [PATCH v6 00/11] ip_pipeline: ip_pipeline application enhancements Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 01/11] ip_pipeline: add parsing for config files with new syntax Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 02/11] ip_pipeline: added config checks Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 03/11] ip_pipeline: modified init to match new params struct Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 04/11] ip_pipeline: moved pipelines to separate folder Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 05/11] ip_pipeline: added master pipeline Maciej Gajdzica
2015-07-08 22:33   ` Thomas Monjalon
2015-07-09  8:03     ` Gajdzica, MaciejX T [this message]
2015-07-09  9:58     ` Gajdzica, MaciejX T
2015-07-09 10:00       ` Dumitrescu, Cristian
2015-07-09 10:06         ` Gajdzica, MaciejX T
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 06/11] ip_pipeline: added application thread Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 07/11] ip_pipeline: moved config files to separate folder Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 08/11] ip_pipeline: added new implementation of passthrough pipeline Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 09/11] ip_pipeline: added new implementation of firewall pipeline Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 10/11] ip_pipeline: added new implementation of routing pipeline Maciej Gajdzica
2015-07-07  8:09 ` [dpdk-dev] [PATCH v6 11/11] ip_pipeline: added new implementation of flow classification pipeline Maciej Gajdzica
2015-07-07  8:27 ` [dpdk-dev] [PATCH v6 00/11] ip_pipeline: ip_pipeline application enhancements Thomas Monjalon
2015-07-07 11:33   ` Dumitrescu, Cristian
2015-07-07  9:23 ` Dumitrescu, Cristian
2015-07-09 15:27   ` 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=9CC680510C0AC140A846FED2EF7F96281384BCDC@IRSMSX102.ger.corp.intel.com \
    --to=maciejx.t.gajdzica@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --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).