From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4]librte_port: modify macros to access packet meta-data
Date: Tue, 20 Oct 2015 14:56:51 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478F23A2@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <6444334.trQLVujQca@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, October 19, 2015 6:00 PM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/4]librte_port: modify macros to access
> packet meta-data
>
> 2015-09-11 14:35, roy.fan.zhang@intel.com:
> > app/test-pipeline/main.h | 2 ++
> > app/test-pipeline/pipeline_hash.c | 34 ++++++++++++++-------------
> > app/test-pipeline/pipeline_lpm.c | 2 +-
> > app/test-pipeline/pipeline_lpm_ipv6.c | 2 +-
> > app/test/test_table.h | 8 +++++--
> > app/test/test_table_combined.c | 28 +++++++++++-----------
> > app/test/test_table_pipeline.c | 3 ++-
> > app/test/test_table_tables.c | 44 ++++++++++++++++++---------------
> --
> > doc/guides/rel_notes/deprecation.rst | 5 ----
> > doc/guides/rel_notes/release_2_2.rst | 4 +++-
> > lib/librte_port/Makefile | 2 +-
> > lib/librte_port/rte_port.h | 2 +-
>
> examples/ip_pipeline does not need to be updated?
No, examples/ip_pipeline does not need to be updated here, so no issues with this patch.
Only apps that define a hardcoded structure for the app metadata need update (app/test, app/test-pipeline), ip_pipeline reads metadata offsets from config file, so it's OK (as current simple config file does not have any offsets).
Thanks,
Cristian
prev parent reply other threads:[~2015-10-20 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 13:35 roy.fan.zhang
2015-09-11 13:35 ` [dpdk-dev] [PATCH 1/4] librte_port: " roy.fan.zhang
2015-09-11 13:35 ` [dpdk-dev] [PATCH 2/4] app/test: modify table and pipeline test roy.fan.zhang
2015-09-11 13:35 ` [dpdk-dev] [PATCH 3/4] app/test_pipeline: modify " roy.fan.zhang
2015-09-11 13:35 ` [dpdk-dev] [PATCH 4/4] librte_port: modify release notes and deprecation notice roy.fan.zhang
2015-10-19 14:21 ` Thomas Monjalon
2015-09-11 13:40 ` [dpdk-dev] [PATCH 0/4]librte_port: modify macros to access packet meta-data Dumitrescu, Cristian
2015-10-19 15:02 ` Thomas Monjalon
[not found] ` <6444334.trQLVujQca@xps13>
2015-10-20 14:56 ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D89126478F23A2@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).