From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH ] event/octeontx2: fix Rx adapter capabilities
Date: Mon, 30 Sep 2019 11:42:55 +0530 [thread overview]
Message-ID: <CALBAE1O0zh+A2go=15qijMoL1PzgOL6PW0UhFqHHtDjtbKeFXg@mail.gmail.com> (raw)
In-Reply-To: <20190819104652.797-1-pbhagavatula@marvell.com>
On Mon, Aug 19, 2019 at 4:17 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Octeontx2 SSO co-processor allows multiple ethernet device Rx queues
> connected to a single Event device queue.
> Fix the Rx adapter capabilities to allow application to configure
> Rx queueus in n:1 ratio to event queues by adding
> `RTE_EVENT_ETH_RX_ADAPTER_CAP_MULTI_EVENTQ` as a capability.
>
> Fixes: 37720fc1fba8 ("event/octeontx2: add Rx adapter")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied to dpdk-next-eventdev/master. Thanks.
> ---
> drivers/event/octeontx2/otx2_evdev_adptr.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/event/octeontx2/otx2_evdev_adptr.c b/drivers/event/octeontx2/otx2_evdev_adptr.c
> index b6e9f59d1..d8a06a593 100644
> --- a/drivers/event/octeontx2/otx2_evdev_adptr.c
> +++ b/drivers/event/octeontx2/otx2_evdev_adptr.c
> @@ -15,7 +15,8 @@ otx2_sso_rx_adapter_caps_get(const struct rte_eventdev *event_dev,
> if (rc)
> *caps = RTE_EVENT_ETH_RX_ADAPTER_SW_CAP;
> else
> - *caps = RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT;
> + *caps = RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT |
> + RTE_EVENT_ETH_RX_ADAPTER_CAP_MULTI_EVENTQ;
>
> return 0;
> }
> --
> 2.22.0
>
prev parent reply other threads:[~2019-09-30 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 10:46 pbhagavatula
2019-09-30 6:12 ` 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='CALBAE1O0zh+A2go=15qijMoL1PzgOL6PW0UhFqHHtDjtbKeFXg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).