From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Rao, GuruprasadX" <guruprasadx.rao@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Chokkalingam, SankarX" <sankarx.chokkalingam@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/test-pipeline: Fix table hash lru initialization
Date: Fri, 23 Sep 2016 14:37:08 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A87D9D@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1474638890-64618-1-git-send-email-guruprasadx.rao@intel.com>
> -----Original Message-----
> From: Rao, GuruprasadX
> Sent: Friday, September 23, 2016 2:55 PM
> To: dev@dpdk.org
> Cc: Chokkalingam, SankarX <sankarx.chokkalingam@intel.com>; Dumitrescu,
> Cristian <cristian.dumitrescu@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>
> Subject: [PATCH] app/test-pipeline: Fix table hash lru initialization
>
> macro ‘APP_METADATA_OFFSET’ was not used to initialize
> ‘signature_offset’ and ‘key_offset’ part of struct
> rte_table_hash_lru_params.
> Instead integer offset values were directly used.
>
> with this fix 'hash-8-lru', 'hash-16-lru', 'hash-32-lru' table types are
> able to forward traffic as expected.
>
> Fixes: 48f31ca50cc4 ("app/pipeline: packet framework benchmark")
>
> Signed-off-by: Sankar Chokkalingam <sankarx.chokkalingam@intel.com>
> Signed-off-by: Guruprasad Rao <guruprasadx.rao@intel.com>
> ---
> app/test-pipeline/pipeline_hash.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2016-09-23 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 13:54 Guruprasad Rao
2016-09-23 14:37 ` Dumitrescu, Cristian [this message]
2016-09-23 17:22 ` 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=3EB4FA525960D640B5BDFFD6A3D8912647A87D9D@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=guruprasadx.rao@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=sankarx.chokkalingam@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 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).