* [dpdk-dev] [PATCH] test/eventdev: use CPU event type
@ 2017-12-04 8:11 Jerin Jacob
2017-12-04 8:44 ` Pavan Nikhilesh Bhagavatula
0 siblings, 1 reply; 3+ messages in thread
From: Jerin Jacob @ 2017-12-04 8:11 UTC (permalink / raw)
To: dev; +Cc: pbhagavatula, Jerin Jacob, stable
octeontx test application was using non RTE_EVENT_TYPE_CPU
event type to generate the event from CPU. Upon the introduction
of ethdev Rx adapter, RTE_EVENT_TYPE_ETHDEV has special
meaning. So avoid using non RTE_EVENT_TYPE_CPU event types
to inject events from CPU.
Fixes: d0d654986018 ("net/octeontx: support event Rx adapter")
Cc: stable@dpdk.org
Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
test/test/test_eventdev_octeontx.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/test/test/test_eventdev_octeontx.c b/test/test/test_eventdev_octeontx.c
index dbc36d948..8fddb4fd2 100644
--- a/test/test/test_eventdev_octeontx.c
+++ b/test/test/test_eventdev_octeontx.c
@@ -355,7 +355,7 @@ generate_random_events(const unsigned int total_events)
for (i = 0; i < total_events; i++) {
ret = inject_events(
rte_rand() % info.max_event_queue_flows /*flow_id */,
- rte_rand() % (RTE_EVENT_TYPE_CPU + 1) /* event_type */,
+ RTE_EVENT_TYPE_CPU /* event_type */,
rte_rand() % 256 /* sub_event_type */,
rte_rand() % (RTE_SCHED_TYPE_PARALLEL + 1),
rte_rand() % queue_count /* queue */,
@@ -745,7 +745,7 @@ test_queue_to_port_single_link(void)
ret = inject_events(
0x100 /*flow_id */,
- rte_rand() % (RTE_EVENT_TYPE_CPU + 1) /* event_type */,
+ RTE_EVENT_TYPE_CPU /* event_type */,
rte_rand() % 256 /* sub_event_type */,
rte_rand() % (RTE_SCHED_TYPE_PARALLEL + 1),
queue /* queue */,
@@ -824,7 +824,7 @@ test_queue_to_port_multi_link(void)
ret = inject_events(
0x100 /*flow_id */,
- rte_rand() % (RTE_EVENT_TYPE_CPU + 1) /* event_type */,
+ RTE_EVENT_TYPE_CPU /* event_type */,
rte_rand() % 256 /* sub_event_type */,
rte_rand() % (RTE_SCHED_TYPE_PARALLEL + 1),
queue /* queue */,
--
2.15.1
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [dpdk-dev] [PATCH] test/eventdev: use CPU event type
2017-12-04 8:11 [dpdk-dev] [PATCH] test/eventdev: use CPU event type Jerin Jacob
@ 2017-12-04 8:44 ` Pavan Nikhilesh Bhagavatula
2017-12-09 9:27 ` Jerin Jacob
0 siblings, 1 reply; 3+ messages in thread
From: Pavan Nikhilesh Bhagavatula @ 2017-12-04 8:44 UTC (permalink / raw)
To: Jerin Jacob; +Cc: dev
On Mon, Dec 04, 2017 at 01:41:18PM +0530, Jerin Jacob wrote:
> octeontx test application was using non RTE_EVENT_TYPE_CPU
> event type to generate the event from CPU. Upon the introduction
> of ethdev Rx adapter, RTE_EVENT_TYPE_ETHDEV has special
> meaning. So avoid using non RTE_EVENT_TYPE_CPU event types
> to inject events from CPU.
>
> Fixes: d0d654986018 ("net/octeontx: support event Rx adapter")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> ---
> test/test/test_eventdev_octeontx.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/test/test/test_eventdev_octeontx.c b/test/test/test_eventdev_octeontx.c
> index dbc36d948..8fddb4fd2 100644
> --- a/test/test/test_eventdev_octeontx.c
> +++ b/test/test/test_eventdev_octeontx.c
> @@ -355,7 +355,7 @@ generate_random_events(const unsigned int total_events)
> for (i = 0; i < total_events; i++) {
> ret = inject_events(
> rte_rand() % info.max_event_queue_flows /*flow_id */,
> - rte_rand() % (RTE_EVENT_TYPE_CPU + 1) /* event_type */,
> + RTE_EVENT_TYPE_CPU /* event_type */,
> rte_rand() % 256 /* sub_event_type */,
> rte_rand() % (RTE_SCHED_TYPE_PARALLEL + 1),
> rte_rand() % queue_count /* queue */,
> @@ -745,7 +745,7 @@ test_queue_to_port_single_link(void)
>
> ret = inject_events(
> 0x100 /*flow_id */,
> - rte_rand() % (RTE_EVENT_TYPE_CPU + 1) /* event_type */,
> + RTE_EVENT_TYPE_CPU /* event_type */,
> rte_rand() % 256 /* sub_event_type */,
> rte_rand() % (RTE_SCHED_TYPE_PARALLEL + 1),
> queue /* queue */,
> @@ -824,7 +824,7 @@ test_queue_to_port_multi_link(void)
>
> ret = inject_events(
> 0x100 /*flow_id */,
> - rte_rand() % (RTE_EVENT_TYPE_CPU + 1) /* event_type */,
> + RTE_EVENT_TYPE_CPU /* event_type */,
> rte_rand() % 256 /* sub_event_type */,
> rte_rand() % (RTE_SCHED_TYPE_PARALLEL + 1),
> queue /* queue */,
> --
> 2.15.1
>
Reviewed-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [dpdk-dev] [PATCH] test/eventdev: use CPU event type
2017-12-04 8:44 ` Pavan Nikhilesh Bhagavatula
@ 2017-12-09 9:27 ` Jerin Jacob
0 siblings, 0 replies; 3+ messages in thread
From: Jerin Jacob @ 2017-12-09 9:27 UTC (permalink / raw)
To: Pavan Nikhilesh Bhagavatula; +Cc: dev
-----Original Message-----
> Date: Mon, 4 Dec 2017 14:14:45 +0530
> From: Pavan Nikhilesh Bhagavatula <pbhagavatula@caviumnetworks.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] test/eventdev: use CPU event type
> User-Agent: NeoMutt/20170609 (1.8.3)
>
> On Mon, Dec 04, 2017 at 01:41:18PM +0530, Jerin Jacob wrote:
> > octeontx test application was using non RTE_EVENT_TYPE_CPU
> > event type to generate the event from CPU. Upon the introduction
> > of ethdev Rx adapter, RTE_EVENT_TYPE_ETHDEV has special
> > meaning. So avoid using non RTE_EVENT_TYPE_CPU event types
> > to inject events from CPU.
> >
> > Fixes: d0d654986018 ("net/octeontx: support event Rx adapter")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > ---
> > test/test/test_eventdev_octeontx.c | 6 +++---
> Reviewed-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Applied to dpdk-next-eventdev/master. Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-12-09 9:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-04 8:11 [dpdk-dev] [PATCH] test/eventdev: use CPU event type Jerin Jacob
2017-12-04 8:44 ` Pavan Nikhilesh Bhagavatula
2017-12-09 9:27 ` Jerin Jacob
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).