DPDK patches and discussions
 help / color / mirror / Atom feed
From: "humin (Q)" <humin29@huawei.com>
To: Fengchengwen <fengchengwen@huawei.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>, dev <dev@dpdk.org>
Cc: thomas <thomas@monjalon.net>
Subject: RE: [PATCH v2 0/2] performance optimized for hns3 PMD
Date: Tue, 16 Nov 2021 15:12:59 +0000	[thread overview]
Message-ID: <F425520D-CC58-4A10-8134-B3E27DD5B1FE> (raw)
In-Reply-To: AB2E8081-4E03-40F8-A4D2-3580EBA58B2D

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

Hi, ferruh,
I forgot it,please added it for me when you merged them.thank you.



________________________________

胡敏 Hu Min
Mobile: +86-13528728164<tel:+86-13528728164>
Email: humin29@huawei.com<mailto:humin29@huawei.com>
发件人:Fengchengwen <fengchengwen@huawei.com>
收件人:Ferruh Yigit <ferruh.yigit@intel.com>;humin (Q) <humin29@huawei.com>;dev <dev@dpdk.org>
抄 送:thomas <thomas@monjalon.net>
时 间:2021-11-16 23:04:08
主 题:RE: [PATCH v2 0/2] performance optimized for hns3 PMD

May be forgotten, I send v2 to him this morning, and maybe forgot adding the sign off. But the patch set is OK because we both check them.


发件人:Ferruh Yigit <ferruh.yigit@intel.com>
收件人:humin (Q) <humin29@huawei.com>;dev <dev@dpdk.org>
抄 送:thomas <thomas@monjalon.net>
时 间:2021-11-16 22:37:23
主 题:Re: [PATCH v2 0/2] performance optimized for hns3 PMD

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?


[-- Attachment #2: Type: text/html, Size: 3459 bytes --]

  parent reply	other threads:[~2021-11-16 15:13 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   ` [PATCH v2 0/2] performance optimized for hns3 PMD Ferruh Yigit
2021-11-16 15:04     ` Fengchengwen
2021-11-16 15:12     ` humin (Q) [this message]
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=F425520D-CC58-4A10-8134-B3E27DD5B1FE \
    --to=humin29@huawei.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@intel.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).