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 v1 0/4] fixes for queue resource free and code style
Date: Thu, 14 May 2020 17:44:55 +0100 [thread overview]
Message-ID: <7ff4f42a-5465-d863-9567-e3327cd1c920@intel.com> (raw)
In-Reply-To: <cover.1589442278.git.cloud.wangxiaoyun@huawei.com>
On 5/14/2020 10:29 AM, Xiaoyun wang wrote:
> This patch adds tx_queues and rx_queues non-null judgment before
> free tx or rx resources, because some app may set tx_queues or
> rx_queues to be null before call free resource interfaces, which
> may cause a segfault, adds pkt_len member update for dst_mbuf
> when copy a mbuf to a new dst_mbuf, code style format rectification,
> and adjusts the legality judgment order of RSS RETA table.
>
> --
> v1:
> - the queues resource free problem fixes
> - the pkt len updates of mbuf fixes
> - code style modification
> - optimize RSS RETA table updates
>
> Xiaoyun wang (4):
> net/hinic: the queues resource free problem fixes
> net/hinic: the pkt len updates of mbuf fixes
> net/hinic: code style modification
> net/hinic: optimize RSS RETA table updates
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-05-14 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 9:29 Xiaoyun wang
2020-05-14 9:29 ` [dpdk-dev] [PATCH v1 1/4] net/hinic: the queues resource free problem fixes Xiaoyun wang
2020-05-14 9:29 ` [dpdk-dev] [PATCH v1 2/4] net/hinic: the pkt len updates of mbuf fixes Xiaoyun wang
2020-05-14 9:29 ` [dpdk-dev] [PATCH v1 3/4] net/hinic: code style modification Xiaoyun wang
2020-05-14 9:29 ` [dpdk-dev] [PATCH v1 4/4] net/hinic: optimize RSS RETA table updates Xiaoyun wang
2020-05-14 16:44 ` 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=7ff4f42a-5465-d863-9567-e3327cd1c920@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).