From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] net/nfp: use Tx ring pointer write back
Date: Thu, 18 Apr 2024 23:14:09 +0100 [thread overview]
Message-ID: <683cc4c2-c83d-47c2-a77d-92a345ad3f98@amd.com> (raw)
In-Reply-To: <20240401065622.106253-1-chaoyong.he@corigine.com>
On 4/1/2024 7:56 AM, Chaoyong He wrote:
> From: Long Wu <long.wu@corigine.com>
>
> This follows the mainline Linux kernel commit
> 0dcf7f500b0a (nfp: use TX ring pointer write back) by Jakub Kicinski.
>
> This will speed up Tx completions, because we avoid a read from
> device memory (replacing PCIe read with DMA read), and it works on
> CoreNIC firmware with NFDk.
>
> Signed-off-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-04-18 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 6:56 Chaoyong He
2024-04-18 22:14 ` Ferruh Yigit [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=683cc4c2-c83d-47c2-a77d-92a345ad3f98@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=long.wu@corigine.com \
--cc=oss-drivers@corigine.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).