From: Jerin Jacob <jerinjacobk@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Abdullah Sevincer <abdullah.sevincer@intel.com>,
stable@dpdk.org
Subject: Re: [PATCH] event/dlb2: fix missing queue ordering capability flag
Date: Fri, 10 Nov 2023 12:55:30 +0530 [thread overview]
Message-ID: <CALBAE1MRet2_M_WXAHo+NW4NhJc1Y9V79iFeheKBw9FLnst9EA@mail.gmail.com> (raw)
In-Reply-To: <20231109174420.788106-1-bruce.richardson@intel.com>
On Thu, Nov 9, 2023 at 11:14 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> The dlb2 driver did not advertise the fact that events could be enqueued
> to it for any queues, not just those in numerical sequence. Add the
> missing bit to the capabilities flag returned from the info_get()
> function.
>
> Fixes: d39e23f26e1e ("event/dlb2: fix advertized capabilities")
> Fixes: e7c9971a857a ("event/dlb2: add probe-time hardware init")
> Cc: stable@dpdk.org
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Waiting for Ack/Review from @Abdullah Sevincer to merge.
> ---
> drivers/event/dlb2/dlb2.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/event/dlb2/dlb2.c b/drivers/event/dlb2/dlb2.c
> index e645f7595a..050ace0904 100644
> --- a/drivers/event/dlb2/dlb2.c
> +++ b/drivers/event/dlb2/dlb2.c
> @@ -72,6 +72,7 @@ static struct rte_event_dev_info evdev_dlb2_default_info = {
> .max_single_link_event_port_queue_pairs =
> DLB2_MAX_NUM_DIR_PORTS(DLB2_HW_V2),
> .event_dev_cap = (RTE_EVENT_DEV_CAP_EVENT_QOS |
> + RTE_EVENT_DEV_CAP_NONSEQ_MODE |
> RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED |
> RTE_EVENT_DEV_CAP_QUEUE_ALL_TYPES |
> RTE_EVENT_DEV_CAP_BURST_MODE |
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-11-10 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 17:44 Bruce Richardson
2023-11-10 7:25 ` Jerin Jacob [this message]
2023-11-12 20:35 ` Sevincer, Abdullah
2023-11-13 5:36 ` 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=CALBAE1MRet2_M_WXAHo+NW4NhJc1Y9V79iFeheKBw9FLnst9EA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abdullah.sevincer@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).