From: "Liu, Jijiang" <jijiang.liu@intel.com>
To: "Walukiewicz, Miroslaw" <Miroslaw.Walukiewicz@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] pmd: add new flag to indicate TX TSO operation on the packet
Date: Tue, 14 Oct 2014 07:47:21 +0000 [thread overview]
Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC01D76B73@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20141013143834.19211.44077.stgit@gklab-18-011.igk.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of
> miroslaw.walukiewicz@intel.com
> Sent: Monday, October 13, 2014 10:39 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 1/3] pmd: add new flag to indicate TX TSO operation
> on the packet
>
> From: Miroslaw Walukiewicz <miroslaw.walukiewicz@intel.com>
>
> Transmission of TCP packets could be accelerated by HW Transmit Segmentation
> Offload. With TSO packets up to 64K could be transmismitted.
>
> When this flag is set the PMD drived will enable TCP segmentation.
>
> The new field tso_segsz is added to indicate how long is TCP TSO segment.
>
> Signed-off-by: Mirek Walukiewicz <miroslaw.walukiewicz@intel.com>
> ---
> lib/librte_mbuf/rte_mbuf.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h index
> ddadc21..63cbc36 100644
> --- a/lib/librte_mbuf/rte_mbuf.h
> +++ b/lib/librte_mbuf/rte_mbuf.h
> @@ -117,6 +117,9 @@ extern "C" {
> /* Use final bit of flags to indicate a control mbuf */
> #define CTRL_MBUF_FLAG (1ULL << 63) /**< Mbuf contains control data */
>
> +/* Bit 50 - TSO (TCP Transmit Segmenation Offload) */
> +#define PKT_TX_TCP_TSO (1ULL << 50) /**< Mbuf needs TSO enabling */
In VxLAN patch set [PATCH v5 7/8]i40e:support VxLAN Tx checksum offload, the bit (1ULL << 50) in offload flag have already been used.
+#define PKT_TX_VXLAN_CKSUM (1ULL << 50) /**< TX checksum of VxLAN computed by NIC */
> /**
> * Bit Mask to indicate what bits required for building TX context
> */
> @@ -196,6 +199,8 @@ struct rte_mbuf {
> uint16_t l2_len:7; /**< L2 (MAC) Header Length. */
> };
> };
> + /* field to support TSO segment size */
> + uint32_t tso_segsz;
> } __rte_cache_aligned;
>
> /**
prev parent reply other threads:[~2014-10-14 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 14:38 miroslaw.walukiewicz
2014-10-13 14:38 ` [dpdk-dev] [PATCH 2/3] pmd: add new header containing TCP offload specific definitions miroslaw.walukiewicz
2014-10-14 9:50 ` Thomas Monjalon
2014-10-13 14:38 ` [dpdk-dev] [PATCH 3/3] pmd i40e: Enable Transmit Segmentation Offload for TCP traffic miroslaw.walukiewicz
2014-10-14 7:47 ` Liu, Jijiang [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=1ED644BD7E0A5F4091CF203DAFB8E4CC01D76B73@SHSMSX101.ccr.corp.intel.com \
--to=jijiang.liu@intel.com \
--cc=Miroslaw.Walukiewicz@intel.com \
--cc=dev@dpdk.org \
/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).