From: Ferruh Yigit <ferruh.yigit@amd.com>
To: longli@linuxonhyperv.com,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: dev@dpdk.org, Ajay Sharma <sharmaajay@microsoft.com>,
Long Li <longli@microsoft.com>
Subject: Re: [Patch v2] net/mana: use the correct WQE count for ringing RQ doorbell
Date: Tue, 11 Jul 2023 11:27:04 +0100 [thread overview]
Message-ID: <7215fdf6-774c-85c6-2cc5-f92c374ddead@amd.com> (raw)
In-Reply-To: <1689033107-4179-1-git-send-email-longli@linuxonhyperv.com>
On 7/11/2023 12:51 AM, longli@linuxonhyperv.com wrote:
> From: Long Li <longli@microsoft.com>
>
> The hardware specification specifies that WQE_COUNT should set to 0 for
> the Receive Queue. Although currently the hardware doesn't enforce the
> check, in the future releases it may check on this value.
>
> Signed-off-by: Long Li <longli@microsoft.com>
>
Is Fixes tag intentionally omitted since change is because of HW / Spec
change, instead of code being wrong when implemented?
next prev parent reply other threads:[~2023-07-11 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 21:35 [PATCH] " longli
2023-07-10 23:51 ` [Patch v2] " longli
2023-07-11 10:27 ` Ferruh Yigit [this message]
2023-07-11 11:01 ` Ferruh Yigit
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=7215fdf6-774c-85c6-2cc5-f92c374ddead@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=sharmaajay@microsoft.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).