From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>
Subject: Re: [PATCH v2 0/2] performance optimized for hns3 PMD
Date: Tue, 16 Nov 2021 14:36:14 +0000 [thread overview]
Message-ID: <f777e0ba-8840-4285-bb11-4170a8c42592@intel.com> (raw)
In-Reply-To: <20211116012212.64819-1-humin29@huawei.com>
On 11/16/2021 1:22 AM, Min Hu (Connor) wrote:
> This patch set contains two ways to optimized Tx performance.
>
> Chengwen Feng (2):
> net/hns3: optimized Tx performance by mbuf fast free
> net/hns3: optimized Tx performance
>
> doc/guides/nics/features/hns3.ini | 1 +
> drivers/net/hns3/hns3_rxtx.c | 129 +++++++++++++++---------------
> drivers/net/hns3/hns3_rxtx.h | 2 +
> drivers/net/hns3/hns3_rxtx_vec.h | 9 +++
> 4 files changed, 77 insertions(+), 64 deletions(-)
> ---
> v2:
> * document hns3.ini and fix 'TE_ETH_TX_OFFLOAD_MBUF_FAST_FREE'
>
Is Connor's sign off in the v1 dropped intentionally, or forgotten?
next prev parent reply other threads:[~2021-11-16 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 13:38 [PATCH " Min Hu (Connor)
2021-11-11 13:38 ` [PATCH 1/2] net/hns3: optimized Tx performance by mbuf fast free Min Hu (Connor)
2021-11-15 17:30 ` Ferruh Yigit
2021-11-16 1:24 ` Min Hu (Connor)
2021-11-11 13:38 ` [PATCH 2/2] net/hns3: optimized Tx performance Min Hu (Connor)
2021-11-15 17:32 ` Ferruh Yigit
2021-11-16 1:22 ` [PATCH v2 0/2] performance optimized for hns3 PMD Min Hu (Connor)
2021-11-16 1:22 ` [PATCH v2 1/2] net/hns3: optimized Tx performance by mbuf fast free Min Hu (Connor)
2021-11-16 1:22 ` [PATCH v2 2/2] net/hns3: optimized Tx performance Min Hu (Connor)
2021-11-16 14:36 ` Ferruh Yigit [this message]
2021-11-16 15:04 ` [PATCH v2 0/2] performance optimized for hns3 PMD Fengchengwen
2021-11-16 15:12 ` humin (Q)
2021-11-16 15:38 ` Ferruh Yigit
2021-11-16 15:43 ` 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=f777e0ba-8840-4285-bb11-4170a8c42592@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=thomas@monjalon.net \
/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).