From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhu, TaoX" <taox.zhu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Zhu, TaoX" <taox.zhu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/iavf: add TSO offload use basic path
Date: Wed, 18 Dec 2019 01:59:57 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153DE3B4D@SHSMSX105.ccr.corp.intel.com> (raw)
In-Reply-To: <20191203152825.51664-1-taox.zhu@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of taox.zhu@intel.com
> Sent: Tuesday, December 3, 2019 11:28 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Zhu, TaoX <taox.zhu@intel.com>
> Subject: [dpdk-dev] [PATCH] net/iavf: add TSO offload use basic path
>
> From: Zhu Tao <taox.zhu@intel.com>
>
> IAVF choices VECTOR TX path or Basic TX path by macro
> IAVF_NO_VECTOR_FLAGS. TSO offload only processed by Basic TX path.
>
> Fixes: 605c6f9ca5 ("net/avf: convert to new Rx and Tx offload API")
>
> Signed-off-by: Zhu Tao <taox.zhu@intel.com>
> ---
> drivers/net/iavf/iavf_rxtx.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/iavf/iavf_rxtx.h b/drivers/net/iavf/iavf_rxtx.h index
> 225a0c4c4..60d02c521 100644
> --- a/drivers/net/iavf/iavf_rxtx.h
> +++ b/drivers/net/iavf/iavf_rxtx.h
> @@ -28,6 +28,7 @@
> DEV_TX_OFFLOAD_VLAN_INSERT | \
> DEV_TX_OFFLOAD_SCTP_CKSUM | \
> DEV_TX_OFFLOAD_UDP_CKSUM | \
> + DEV_TX_OFFLOAD_TCP_TSO | \
> DEV_TX_OFFLOAD_TCP_CKSUM)
>
> #define DEFAULT_TX_RS_THRESH 32
> --
> 2.17.1
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
next prev parent reply other threads:[~2019-12-18 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 15:28 [dpdk-dev] [PATCH] net/iavf: add TSO offload use basic path taox.zhu
2019-12-18 1:59 ` Zhang, Qi Z [this message]
2019-12-18 2:14 ` Ye Xiaolong
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=039ED4275CED7440929022BC67E7061153DE3B4D@SHSMSX105.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=taox.zhu@intel.com \
--cc=wenzhuo.lu@intel.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).