From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Nipun Gupta <nipun.gupta@nxp.com>, <dev@dpdk.org>
Cc: <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] event/dpaa2: return correct number of event ports
Date: Fri, 12 Jan 2018 20:12:27 +0530 [thread overview]
Message-ID: <9aed1d0e-87f5-2582-42cc-b7eeef8a5a23@nxp.com> (raw)
In-Reply-To: <1514997859-3902-1-git-send-email-nipun.gupta@nxp.com>
On 1/3/2018 10:14 PM, Nipun Gupta wrote:
> In the info get API we were returning number of event
> ports as MAX number of LCORE's. After this change actual
> number of event ports (i.e. number of DPIO's) is provided
> in the info get API.
>
> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> ---
> This patch is dependent on https://dpdk.org/dev/patchwork/patch/32834/
> as it uses the API exposed in the mentioned patch
>
> drivers/event/dpaa2/dpaa2_eventdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/event/dpaa2/dpaa2_eventdev.c b/drivers/event/dpaa2/dpaa2_eventdev.c
> index 13e7122..5cbe1cf 100644
> --- a/drivers/event/dpaa2/dpaa2_eventdev.c
> +++ b/drivers/event/dpaa2/dpaa2_eventdev.c
> @@ -326,7 +326,7 @@ static void dpaa2_eventdev_process_atomic(struct qbman_swp *swp,
> DPAA2_EVENT_MAX_QUEUE_PRIORITY_LEVELS;
> dev_info->max_event_priority_levels =
> DPAA2_EVENT_MAX_EVENT_PRIORITY_LEVELS;
> - dev_info->max_event_ports = RTE_MAX_LCORE;
> + dev_info->max_event_ports = rte_fslmc_get_device_count(DPAA2_IO);
> dev_info->max_event_port_dequeue_depth =
> DPAA2_EVENT_MAX_PORT_DEQUEUE_DEPTH;
> dev_info->max_event_port_enqueue_depth =
>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2018-01-12 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 16:44 Nipun Gupta
2018-01-12 14:42 ` Hemant Agrawal [this message]
2018-01-18 7:04 ` Jerin Jacob
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=9aed1d0e-87f5-2582-42cc-b7eeef8a5a23@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nipun.gupta@nxp.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).