DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>, dev@dpdk.org
Cc: bluca@debian.org, luoxianjun@huawei.com, luoxingyu@huawei.com,
	zhouguoyang@huawei.com, shahar.belkar@huawei.com,
	yin.yinshi@huawei.com
Subject: Re: [dpdk-dev] [PATCH v4 0/3] Fix and add txq xstats
Date: Fri, 10 Apr 2020 14:42:46 +0100	[thread overview]
Message-ID: <e9b0cb00-79df-73dc-af3e-2d0533d42621@intel.com> (raw)
In-Reply-To: <cover.1586508802.git.cloud.wangxiaoyun@huawei.com>

On 4/10/2020 10:21 AM, Xiaoyun wang wrote:
> This patch fixes PF firmware hotactive problem, optimizes
> log style and adds txq xstats members.
> 
> --
> v3->v4:
>   - fix PF firmware hotactive problem
>   - optimize log style
>   - adds txq xstats members
>   
> v2->v3:
>   - fix FW hotactive problem
>   - optimize log style
>   
> v1->v2:
>   - Fix LRO problems
>   - Fix hotupdate firmware problem
>   - Optimize doorbell area initialization 
>   - Remove 40GE Mezz card id
>   - Add Fdir filter type
>   - Optimize log files
>   - Support pause flow control
> 
> v1:
>   - Allocate IO memory with socketid
> 
> Xiaoyun wang (3):
>   net/hinic/base: fix PF firmware hotactive problem
>   net/hinic/base: optimize log style
>   net/hinic: adds txq xstats member
> 

Series applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2020-04-10 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  9:21 Xiaoyun wang
2020-04-10  9:21 ` [dpdk-dev] [PATCH v4 1/3] net/hinic/base: fix PF firmware hotactive problem Xiaoyun wang
2020-04-10  9:21 ` [dpdk-dev] [PATCH v4 2/3] net/hinic/base: optimize log style Xiaoyun wang
2020-04-10  9:21 ` [dpdk-dev] [PATCH v4 3/3] net/hinic: adds txq xstats member Xiaoyun wang
2020-04-10 13:42 ` 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=e9b0cb00-79df-73dc-af3e-2d0533d42621@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=luoxianjun@huawei.com \
    --cc=luoxingyu@huawei.com \
    --cc=shahar.belkar@huawei.com \
    --cc=yin.yinshi@huawei.com \
    --cc=zhouguoyang@huawei.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).