From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pravin Pathak <pravin.pathak@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, mike.ximing.chen@intel.com,
bruce.richardson@intel.com, thomas@monjalon.net,
david.marchand@redhat.com, nipun.gupta@amd.com,
chenbox@nvidia.com, tirthendu.sarkar@intel.com
Subject: Re: [PATCH v2 1/7] event/dlb2: addresses deq failure when CQ depth <= 16
Date: Wed, 4 Jun 2025 14:28:58 +0530 [thread overview]
Message-ID: <CALBAE1NS4YRZFqGe2s1wQqtNyr9vQe+zL2eU2kfXXAijxpaCig@mail.gmail.com> (raw)
In-Reply-To: <20250603180514.3826917-2-pravin.pathak@intel.com>
On Tue, Jun 3, 2025 at 11:47 PM Pravin Pathak <pravin.pathak@intel.com> wrote:
>
> When application configures a DIR port with CQ depth less than 8, DLB PMD
> sets port's cq_depth as 8 and token reservation is used to make the
> effective cq_depth smaller. However, while setting port's cq_depth_mask
> application configured CQ depth was used resulting in reading incorrect
> cachelines while dequeuing. Use PMD calculated CQ depth for cq_depth_mask
> calculation.
>
> Signed-off-by: Pravin Pathak <pravin.pathak@intel.com>
> Signed-off-by: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
it looks like except 4/7 remaining patches are fixes. please change
relevant patches subject to event/dlb2: fix ...
and add Fixes tag,
next prev parent reply other threads:[~2025-06-04 8:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 4:23 [PATCH v1 0/7] event/dlb2: dlb2 hw resource management Pravin Pathak
2025-05-09 4:23 ` [PATCH v1 1/7] event/dlb2: addresses deq failure when CQ depth <= 16 Pravin Pathak
2025-05-09 4:23 ` [PATCH v1 2/7] event/dlb2: changes to correctly validate COS ID arguments Pravin Pathak
2025-05-09 4:23 ` [PATCH v1 3/7] event/dlb2: return 96 single link ports for DLB2.5 Pravin Pathak
2025-05-27 5:46 ` [EXTERNAL] " Jerin Jacob
2025-05-09 4:23 ` [PATCH v1 4/7] event/dlb2: support managing history list resource Pravin Pathak
2025-05-27 5:50 ` [EXTERNAL] " Jerin Jacob
2025-05-27 5:57 ` Jerin Jacob
2025-05-27 13:16 ` Thomas Monjalon
2025-05-09 4:23 ` [PATCH v1 5/7] event/dlb2: avoid credit release race condition Pravin Pathak
2025-05-09 4:24 ` [PATCH v1 6/7] event/dlb2: update qid depth xstat in vector path Pravin Pathak
2025-05-09 4:24 ` [PATCH v1 7/7] event/dlb2: fix default credits in dlb2_eventdev_info_get() Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 0/7] event/dlb2: dlb2 hw resource management Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 1/7] event/dlb2: addresses deq failure when CQ depth <= 16 Pravin Pathak
2025-06-04 8:58 ` Jerin Jacob [this message]
2025-06-03 18:05 ` [PATCH v2 2/7] event/dlb2: changes to correctly validate COS ID arguments Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 3/7] event/dlb2: return 96 single link ports for DLB2.5 Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 4/7] event/dlb2: support managing history list resource Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 5/7] event/dlb2: avoid credit release race condition Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 6/7] event/dlb2: update qid depth xstat in vector path Pravin Pathak
2025-06-03 18:05 ` [PATCH v2 7/7] event/dlb2: return default credits based on HW version Pravin Pathak
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=CALBAE1NS4YRZFqGe2s1wQqtNyr9vQe+zL2eU2kfXXAijxpaCig@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.com \
--cc=nipun.gupta@amd.com \
--cc=pravin.pathak@intel.com \
--cc=thomas@monjalon.net \
--cc=tirthendu.sarkar@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).