DPDK patches and discussions
 help / color / mirror / Atom feed
From: gowrishankar muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
To: Chao Zhu <chaozhu@linux.vnet.ibm.com>, dev@dpdk.org
Cc: "'Bruce Richardson'" <bruce.richardson@intel.com>,
	"'Konstantin Ananyev'" <konstantin.ananyev@intel.com>,
	"'Thomas Monjalon'" <thomas.monjalon@6wind.com>,
	"'Cristian Dumitrescu'" <cristian.dumitrescu@intel.com>,
	"'Pradeep'" <pradeep@us.ibm.com>
Subject: Re: [dpdk-dev] [PATCH v5 4/8] table: enable table library for ppc64le
Date: Tue, 16 Aug 2016 16:04:51 +0530	[thread overview]
Message-ID: <ea617f36-a4e8-29b0-1319-eb274957fa50@linux.vnet.ibm.com> (raw)
In-Reply-To: <000001d1f793$b93a8b90$2bafa2b0$@linux.vnet.ibm.com>

Thanks Chao for bringing up.

I had fixed one of .c earlier before rebasing to master. I then dropped 
the patch
while decoupling ppc enablement and bug fixes. Now I realize on why we need
this fix as part of enabling table in ppc completely. So, added one 
additional patch
separately fixing this in v6. After this patch, a ltable lib unit test 
fail as in Intel case
currently and it is not related to powerpc changes.

If some one already looking into broken unit test failure for table lib, 
that is helpful.

Regards,
Gowrishankar

On Tuesday 16 August 2016 01:26 PM, Chao Zhu wrote:
> Gowrishankar,
>
> The unit test of table got failed.
> When I took a look at the code, it failed on this line in file
> lib/librte_table/rte_table_hash_key8.c ,
> lib/librte_table/rte_table_hash_key16.c,
> lib/librte_table/rte_table_hash_key32.c:
>
> 	if ((check_params_create_lru(p) != 0) ||
> 		((sizeof(struct rte_table_hash) % RTE_CACHE_LINE_SIZE) != 0)
> ||
> 		((sizeof(struct rte_bucket_4_8) % RTE_CACHE_LINE_SIZE) !=
> 0)) {
> 		return NULL;
> 	}
>
> 	if ((check_params_create_lru(p) != 0) ||
> 		((sizeof(struct rte_table_hash) % RTE_CACHE_LINE_SIZE) != 0)
> ||
> 		((sizeof(struct rte_bucket_4_16) % RTE_CACHE_LINE_SIZE) !=
> 0)) {
> 		return NULL;
> 	}
>
> 	if ((check_params_create_lru(p) != 0) ||
> 		((sizeof(struct rte_table_hash) % RTE_CACHE_LINE_SIZE) != 0)
> ||
> 		((sizeof(struct rte_bucket_4_32) % RTE_CACHE_LINE_SIZE) !=
> 0)) {
> 		return NULL;
> 	}
>
> The size of rte_bucket_4_8/16/32 is not aligned to cache line size. This is
> normal, because POWER has different cache line size. The change of struct
> rte_bucket_4_8/16/32 may solve this problem. I didn't do further
> investigation. Can you help to double check this patch?
>
>
> -----Original Message-----
> From: Gowrishankar Muthukrishnan [mailto:gowrishankar.m@linux.vnet.ibm.com]
> Sent: 2016年8月12日 20:03
> To: dev@dpdk.org
> Cc: Chao Zhu <chaozhu@linux.vnet.ibm.com>; Bruce Richardson
> <bruce.richardson@intel.com>; Konstantin Ananyev
> <konstantin.ananyev@intel.com>; Thomas Monjalon <thomas.monjalon@6wind.com>;
> Cristian Dumitrescu <cristian.dumitrescu@intel.com>; Pradeep
> <pradeep@us.ibm.com>; gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
> Subject: [PATCH v5 4/8] table: enable table library for ppc64le
>
> From: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
>
> This patch enables librte_table in ppc64le.
>
> Signed-off-by: Gowrishankar Muthukrishnan
> <gowrishankar.m@linux.vnet.ibm.com>
> ---
>   config/defconfig_ppc_64-power8-linuxapp-gcc | 1 -
>   1 file changed, 1 deletion(-)
>
> diff --git a/config/defconfig_ppc_64-power8-linuxapp-gcc
> b/config/defconfig_ppc_64-power8-linuxapp-gcc
> index dede34f..41f67d5 100644
> --- a/config/defconfig_ppc_64-power8-linuxapp-gcc
> +++ b/config/defconfig_ppc_64-power8-linuxapp-gcc
> @@ -59,5 +59,4 @@ CONFIG_RTE_LIBRTE_FM10K_PMD=n  # This following libraries
> are not available on Power. So they're turned off.
>   CONFIG_RTE_LIBRTE_SCHED=n
>   CONFIG_RTE_LIBRTE_PORT=n
> -CONFIG_RTE_LIBRTE_TABLE=n
>   CONFIG_RTE_LIBRTE_PIPELINE=n
> --
> 1.9.1
>
>
>

  reply	other threads:[~2016-08-16 10:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12 12:03 [dpdk-dev] [PATCH v5 0/8] enable lpm, acl and other missing libraries in ppc64le Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 1/8] lpm: add altivec intrinsics for dpdk lpm on ppc_64 Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 2/8] acl: add altivec intrinsics for dpdk acl " Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 3/8] l3fwd: add altivec support for em_hash_key Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 4/8] table: enable table library for ppc64le Gowrishankar Muthukrishnan
2016-08-16  7:56   ` Chao Zhu
2016-08-16 10:34     ` gowrishankar muthukrishnan [this message]
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 5/8] sched: enable sched " Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 6/8] port: enable port " Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 7/8] pipeline: enable pipeline " Gowrishankar Muthukrishnan
2016-08-12 12:03 ` [dpdk-dev] [PATCH v5 8/8] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64 Gowrishankar Muthukrishnan

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=ea617f36-a4e8-29b0-1319-eb274957fa50@linux.vnet.ibm.com \
    --to=gowrishankar.m@linux.vnet.ibm.com \
    --cc=bruce.richardson@intel.com \
    --cc=chaozhu@linux.vnet.ibm.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=pradeep@us.ibm.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).