From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>, dev@dpdk.org
Cc: bluca@debian.org, luoxianjun@huawei.com, zhouguoyang@huawei.com,
yin.yinshi@huawei.com, david.yangxiaoliang@huawei.com,
zhaohui8@huawei.com, zhengjingzhou@huawei.com,
guojian365@huawei.com
Subject: Re: [dpdk-dev] [PATCH v2 0/4] some bugs fixes
Date: Tue, 28 Jul 2020 11:41:40 +0100 [thread overview]
Message-ID: <7cbcdf14-01b2-0ea5-5f57-436973361f04@intel.com> (raw)
In-Reply-To: <cover.1595663173.git.cloud.wangxiaoyun@huawei.com>
On 7/25/2020 9:15 AM, Xiaoyun wang wrote:
> These patches modify csum offload process, optimize Rx
> performance for x86, set vhd type with 2 for no offset
> in ovs offload scenario, make timeout not affected by
> system time jump.
>
> --
> v1->v2:
> - fix typo spelling
>
> v1:
> - modify csum offload process
> - optimize Rx performance for x86
> - modify vhd type for SDI
> - make timeout not affected by system time jump
>
> Xiaoyun wang (4):
> net/hinic: modify csum offload process
> net/hinic: optimize Rx performance for x86
> net/hinic/base: modify vhd type for SDI
> net/hinic/base: make timeout not affected by system time jump
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-07-28 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 8:15 [dpdk-dev] [PATCH v2 0/4] some bugs fixes Xiaoyun wang
2020-07-25 8:15 ` [dpdk-dev] [PATCH v2 1/4] net/hinic: modify csum offload process Xiaoyun wang
2020-07-25 8:15 ` [dpdk-dev] [PATCH v2 2/4] net/hinic: optimize Rx performance for x86 Xiaoyun wang
2020-07-25 8:15 ` [dpdk-dev] [PATCH v2 3/4] net/hinic/base: modify vhd type for SDI Xiaoyun wang
2020-07-25 8:15 ` [dpdk-dev] [PATCH v2 4/4] net/hinic/base: make timeout not affected by system time jump Xiaoyun wang
2020-07-28 10:41 ` 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=7cbcdf14-01b2-0ea5-5f57-436973361f04@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=guojian365@huawei.com \
--cc=luoxianjun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.