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, david.yangxiaoliang@huawei.com,
	zhaohui8@huawei.com, zhengjingzhou@huawei.com
Subject: Re: [dpdk-dev] [PATCH v5 0/4] Support ipv6 flow rules
Date: Mon, 11 May 2020 21:20:57 +0100	[thread overview]
Message-ID: <d95a5f49-91e3-4c0d-643d-0c6a8a0c8863@intel.com> (raw)
In-Reply-To: <0ecab847-a882-838b-2bf1-8b1b5a8e0f4b@intel.com>

On 5/11/2020 8:04 PM, Ferruh Yigit wrote:
> On 5/9/2020 5:04 AM, Xiaoyun wang wrote:
>> This patch adds jumbo frame offload flag, increases
>> judgment whether Tx/Rx queues is non-null when free
>> resources, and if card mode does not support nic, 
>> driver will be initialized failed, supports ipv6
>> flow director for BGP or ICMP packets.
>>
>> --
>> v4->v5:
>>   - increase Tx/Rx queues non-null judgment
>>   - add jumbo frame offload flag
>>   - increase judgment for support NIC or not
>>   - support ipv6 flow rules
>>   
>> 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 (4):
>>   net/hinic: increase Tx/Rx queues non-null judgment
>>   net/hinic: add jumbo frame offload flag
>>   net/hinic: increase judgment for support NIC or not
>>   net/hinic/base: support ipv6 flow rules
>>
> 
> Hi Xiaoyun,
> 
> Some of above are separate patchsets, and previous ones already merged. I guess
> there is a confusion about versioning (vN) in patchsets.
> 
> The versioning is a new version of patchset if a new version required/requested.
> It is not incremental changes to a driver (or a component)
> 
> The previous patchset has been applied in v4, for this new patchset it should
> start from v1 again.
> 
> (Also previous v2 and v3 were different patchsets, and should reset the
> versioning ... )
> 

Hi Xiaoyun,

It looks patches in the set don't depend on each other, so I will get the set
partially, except patch 1/4, to be able to include them into the -rc2 release.
(Otherwise it may not be possible to merge flow API patch in -rc3 or later.)

Please send the patch 1/4 separately.

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

      reply	other threads:[~2020-05-11 20:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  4:04 Xiaoyun wang
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 1/4] net/hinic: increase Tx/Rx queues non-null judgment Xiaoyun wang
2020-05-11 19:09   ` Ferruh Yigit
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 2/4] net/hinic: add jumbo frame offload flag Xiaoyun wang
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 3/4] net/hinic: increase judgment for support NIC or not Xiaoyun wang
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 4/4] net/hinic/base: support ipv6 flow rules Xiaoyun wang
2020-05-11 20:12   ` Ferruh Yigit
2020-05-11 19:04 ` [dpdk-dev] [PATCH v5 0/4] Support " Ferruh Yigit
2020-05-11 20:20   ` 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=d95a5f49-91e3-4c0d-643d-0c6a8a0c8863@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=david.yangxiaoliang@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=zhaohui8@huawei.com \
    --cc=zhengjingzhou@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).