From: Jakub Kicinski <kuba@kernel.org>
To: longli@linuxonhyperv.com
Cc: Paolo Abeni <pabeni@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
Ajay Sharma <sharmaajay@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-rdma@vger.kernel.org, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Long Li <longli@microsoft.com>,
stable@vger.kernel.org
Subject: Re: [Patch v3] net: mana: Batch ringing RX queue doorbell on receiving packets
Date: Thu, 29 Jun 2023 09:11:29 -0700 [thread overview]
Message-ID: <20230629091129.19217388@kernel.org> (raw)
In-Reply-To: <36c95dd6babb2202f70594d5dde13493af62dcad.camel@redhat.com>
On Thu, 29 Jun 2023 10:42:34 +0200 Paolo Abeni wrote:
> > While we are making changes in this code path, change the code for
> > ringing doorbell to set the WQE_COUNT to 0 for Receive Queue. The
> > hardware specification specifies that it should set to 0. Although
> > currently the hardware doesn't enforce the check, in the future releases
> > it may do.
And please split this cleanup into a separate patch, it doesn't sound
like it has to be done as part of the optimization.
next prev parent reply other threads:[~2023-06-29 16:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:57 [Patch v3] net: mana: Batch ringing RX queue doorbell on receiving packets longli
2023-06-29 8:42 ` Paolo Abeni
2023-06-29 16:11 ` Jakub Kicinski [this message]
2023-06-29 18:19 ` Long Li
2023-06-29 16:53 ` Haiyang Zhang
2023-06-29 17:06 ` Jakub Kicinski
2023-06-29 18:18 ` Long Li
2023-06-30 10:36 ` Paolo Abeni
2023-06-30 17:31 ` Long Li
2023-06-30 19:46 ` Greg KH
2023-06-30 20:42 ` Long Li
2023-06-30 23:38 ` Jakub Kicinski
2023-07-02 20:18 ` Long Li
2023-07-03 10:14 ` Paolo Abeni
2023-07-06 17:51 ` Long Li
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=20230629091129.19217388@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharmaajay@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=wei.liu@kernel.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).