From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Nipun Gupta <nipun.gupta@nxp.com>
Cc: dev@dpdk.org, hemant.agarwal@nxp.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] event/dpaa2: advertise the burst mode capability
Date: Wed, 19 Jul 2017 20:15:57 +0530 [thread overview]
Message-ID: <20170719144556.GA18235@jerin> (raw)
In-Reply-To: <1500473912-24602-1-git-send-email-nipun.gupta@nxp.com>
-----Original Message-----
> Date: Wed, 19 Jul 2017 19:48:32 +0530
> From: Nipun Gupta <nipun.gupta@nxp.com>
> To: dev@dpdk.org
> CC: hemant.agarwal@nxp.com, jerin.jacob@caviumnetworks.com,
> thomas@monjalon.net, Nipun Gupta <nipun.gupta@nxp.com>
> Subject: [PATCH] event/dpaa2: advertise the burst mode capability
> X-Mailer: git-send-email 1.9.1
>
> Burst mode capability flag was introduced in 73e6b8c9 for event drivers.
> DPAA2 event driver supports burst mode so this patch adds this capability
> flag in DPAA2 event driver
>
> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
Reviewed-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> ---
> drivers/event/dpaa2/dpaa2_eventdev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/event/dpaa2/dpaa2_eventdev.c b/drivers/event/dpaa2/dpaa2_eventdev.c
> index ed57376..cf2d274 100644
> --- a/drivers/event/dpaa2/dpaa2_eventdev.c
> +++ b/drivers/event/dpaa2/dpaa2_eventdev.c
> @@ -315,7 +315,8 @@ static void dpaa2_eventdev_process_atomic(struct qbman_swp *swp,
> dev_info->max_event_port_enqueue_depth =
> DPAA2_EVENT_MAX_PORT_ENQUEUE_DEPTH;
> dev_info->max_num_events = DPAA2_EVENT_MAX_NUM_EVENTS;
> - dev_info->event_dev_cap = RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED;
> + dev_info->event_dev_cap = RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED |
> + RTE_EVENT_DEV_CAP_BURST_MODE;
> }
>
> static int
> --
> 1.9.1
>
prev parent reply other threads:[~2017-07-19 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 14:18 Nipun Gupta
2017-07-19 14:45 ` Jerin Jacob [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=20170719144556.GA18235@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=hemant.agarwal@nxp.com \
--cc=nipun.gupta@nxp.com \
--cc=thomas@monjalon.net \
/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).