Re: [dpdk-dev] [dpdk-stable] [PATCH 2/2] test/rcu: address test case failure

2019-06-28 Thread David Marchand
On Fri, Jun 28, 2019 at 6:37 PM Honnappa Nagarahalli < honnappa.nagaraha...@arm.com> wrote: > On Fri, Jun 28, 2019 at 5:44 AM Honnappa Nagarahalli < > honnappa.nagaraha...@arm.com> wrote: > Test case for rte_rcu_qsbr_get_memsize is written specifically > for 12

Re: [dpdk-dev] [dpdk-stable] [PATCH 2/2] test/rcu: address test case failure

2019-06-28 Thread Honnappa Nagarahalli
On Fri, Jun 28, 2019 at 5:44 AM Honnappa Nagarahalli mailto:honnappa.nagaraha...@arm.com>> wrote: Test case for rte_rcu_qsbr_get_memsize is written specifically for 128 threads. Do not use RTE_MAX_LCORE as it changes for different configurations. Does it mean this test can only work on arm with 2

Re: [dpdk-dev] [dpdk-stable] [PATCH 2/2] test/rcu: address test case failure

2019-06-28 Thread David Marchand
On Fri, Jun 28, 2019 at 3:54 PM Honnappa Nagarahalli < honnappa.nagaraha...@arm.com> wrote: > > > On Fri, Jun 28, 2019 at 5:44 AM Honnappa Nagarahalli < > honnappa.nagaraha...@arm.com> wrote: > > Test case for rte_rcu_qsbr_get_memsize is written specifically > for 128 threads. Do not use RTE_MAX_L

Re: [dpdk-dev] [dpdk-stable] [PATCH 2/2] test/rcu: address test case failure

2019-06-28 Thread Honnappa Nagarahalli
On Fri, Jun 28, 2019 at 5:44 AM Honnappa Nagarahalli mailto:honnappa.nagaraha...@arm.com>> wrote: Test case for rte_rcu_qsbr_get_memsize is written specifically for 128 threads. Do not use RTE_MAX_LCORE as it changes for different configurations. Does it mean this test can only work on arm with

Re: [dpdk-dev] [dpdk-stable] [PATCH 2/2] test/rcu: address test case failure

2019-06-28 Thread David Marchand
On Fri, Jun 28, 2019 at 5:44 AM Honnappa Nagarahalli < honnappa.nagaraha...@arm.com> wrote: > Test case for rte_rcu_qsbr_get_memsize is written specifically > for 128 threads. Do not use RTE_MAX_LCORE as it changes for > different configurations. > Does it mean this test can only work on arm with