From: Jerin Jacob <jerinjacobk@gmail.com>
To: Timothy McDaniel <timothy.mcdaniel@intel.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH v3] event/dlb2: fix advertized capabilities
Date: Tue, 14 Jun 2022 14:56:45 +0530 [thread overview]
Message-ID: <CALBAE1NqdhHeuQwGyz7U2kDDe-bNWzA=eW2ewRbuPyZ6rPHf6A@mail.gmail.com> (raw)
In-Reply-To: <20220613181914.3212778-1-timothy.mcdaniel@intel.com>
On Mon, Jun 13, 2022 at 11:49 PM Timothy McDaniel
<timothy.mcdaniel@intel.com> wrote:
>
> This commit corrects the advertized capabilities reported by the DLB2 PMD.
>
> Previously DLB2 reported supporting RTE_EVENT_DEV_CAP_QUEUE_QOS, but the
> DLB2 hardware does not support such capability. This commit removes that
> feature from the reported capabilities feature set.
>
> Additionally, two capabilities that DLB2 does support were not being
> reported in the capabilities feature set. This commit adds those.
>
> RTE_EVENT_DEV_CAP_MULTIPLE_QUEUE_PORT = Event device is capable of
> setting up the link between multiple queues and a single port. If the
> flag is not set, the eventdev can only map a single queue to each
> port or map a single queue to many port
>
> RTE_EVENT_DEV_CAP_RUNTIME_PORT_LINK = Event device is capable of
> configuring the queue/port link at runtime. If the flag is not set,
> the eventdev queue/port link is only can be configured during
> initialization
>
> Finally, the file doc/guides/eventdevs/features/dlb2.ini has been updated
> to match the capabilities actually reported by the PMD.
>
> Fixes: e7c9971a857a ("event/dlb2: add probe-time hardware init")
> Cc: stable@dpdk.org
>
> Signed-off-by: Timothy McDaniel <timothy.mcdaniel@intel.com>
>
For here to [2] content, needs to be moved to [1] to avoid polluting
the commit message.
Fixed and Applied to dpdk-next-net-eventdev/for-main. Thanks
> ===
>
> Changes since V2:
> Added "fixes" line that was present in original, but missing in V2.
>
> Changes since V1;
> 1) reorder capabilities flags to match the order that they appear in
> in the default.ini file
> 2) update the dlb2.ini file with the new set of features supported by DLB2
> 3) expanded the commit message to provide additional details
[2]
> ---
[1]
> doc/guides/eventdevs/features/dlb2.ini | 3 ++-
prev parent reply other threads:[~2022-06-14 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:40 [PATCH] " Timothy McDaniel
2022-06-09 17:05 ` Jerin Jacob
2022-06-09 18:02 ` McDaniel, Timothy
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 [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='CALBAE1NqdhHeuQwGyz7U2kDDe-bNWzA=eW2ewRbuPyZ6rPHf6A@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=stable@dpdk.org \
--cc=timothy.mcdaniel@intel.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).