From: miroslaw.walukiewicz@intel.com
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] pmd: add new flag to indicate TX TSO operation on the packet
Date: Mon, 13 Oct 2014 10:38:34 -0400 [thread overview]
Message-ID: <20141013143834.19211.44077.stgit@gklab-18-011.igk.intel.com> (raw)
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 */
+
/**
* 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;
/**
next reply other threads:[~2014-10-13 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 14:38 miroslaw.walukiewicz [this message]
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 ` [dpdk-dev] [PATCH 1/3] pmd: add new flag to indicate TX TSO operation on the packet Liu, Jijiang
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=20141013143834.19211.44077.stgit@gklab-18-011.igk.intel.com \
--to=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).