From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: RE: [PATCH] event/dlb2: fix advertized capabilities
Date: Thu, 9 Jun 2022 18:02:11 +0000 [thread overview]
Message-ID: <SN6PR11MB3103B7EE4C5A31EAA56446399EA79@SN6PR11MB3103.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1P9KK1MHSnA=YDunDomS_8uw_c=ZiREerodsLdWQ_2htA@mail.gmail.com>
I will update both the description and doc/guides/eventdevs/features/dlb2.ini
Thanks,
Tim
> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Thursday, June 9, 2022 12:06 PM
> To: McDaniel, Timothy <timothy.mcdaniel@intel.com>
> Cc: Jerin Jacob <jerinj@marvell.com>; dpdk-dev <dev@dpdk.org>; dpdk stable
> <stable@dpdk.org>
> Subject: Re: [PATCH] event/dlb2: fix advertized capabilities
>
> On Mon, Jun 6, 2022 at 9:31 PM Timothy McDaniel
> <timothy.mcdaniel@intel.com> wrote:
> >
>
> Be more descriptive,
>
> > 1) Remove RTE_EVENT_DEV_CAP_QUEUE_QOS. DLB/DLB2 do not support
> > queue priority
> > 2) Add RTE_EVENT_DEV_CAP_MULTIPLE_QUEUE_PORT
> > 3) Add RTE_EVENT_DEV_CAP_RUNTIME_PORT_LINK
>
> file doc/guides/eventdevs/features/dlb2.ini is not updated. It is out of sync.
>
> >
> > Fixes: e7c9971a857a ("event/dlb2: add probe-time hardware init")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Timothy McDaniel <timothy.mcdaniel@intel.com>
> > ---
> > drivers/event/dlb2/dlb2.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/event/dlb2/dlb2.c b/drivers/event/dlb2/dlb2.c
> > index 36f07d0061..5c30d5ce35 100644
> > --- a/drivers/event/dlb2/dlb2.c
> > +++ b/drivers/event/dlb2/dlb2.c
> > @@ -61,11 +61,12 @@ static struct rte_event_dev_info
> evdev_dlb2_default_info = {
> > .max_num_events = DLB2_MAX_NUM_LDB_CREDITS,
> > .max_single_link_event_port_queue_pairs =
> > DLB2_MAX_NUM_DIR_PORTS(DLB2_HW_V2),
> > - .event_dev_cap = (RTE_EVENT_DEV_CAP_QUEUE_QOS |
> > - RTE_EVENT_DEV_CAP_EVENT_QOS |
> > + .event_dev_cap = (RTE_EVENT_DEV_CAP_EVENT_QOS |
> > RTE_EVENT_DEV_CAP_BURST_MODE |
> > RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED |
> > RTE_EVENT_DEV_CAP_IMPLICIT_RELEASE_DISABLE |
> > + RTE_EVENT_DEV_CAP_MULTIPLE_QUEUE_PORT |
> > + RTE_EVENT_DEV_CAP_RUNTIME_PORT_LINK |
> > RTE_EVENT_DEV_CAP_QUEUE_ALL_TYPES |
> > RTE_EVENT_DEV_CAP_MAINTENANCE_FREE),
> > };
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2022-06-09 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:40 Timothy McDaniel
2022-06-09 17:05 ` Jerin Jacob
2022-06-09 18:02 ` McDaniel, Timothy [this message]
2022-06-10 18:36 ` [PATCH v2] " Timothy McDaniel
2022-06-13 6:21 ` Jerin Jacob
2022-06-13 18:19 ` [PATCH v3] " Timothy McDaniel
2022-06-14 9:26 ` 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=SN6PR11MB3103B7EE4C5A31EAA56446399EA79@SN6PR11MB3103.namprd11.prod.outlook.com \
--to=timothy.mcdaniel@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--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).