DPDK patches and discussions
 help / color / mirror / Atom feed
From: miroslaw.walukiewicz@intel.com
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] pmd: Add generic support for TCP TSO (Transmit Segmentation Offload)
Date: Mon, 20 Oct 2014 05:42:52 -0400	[thread overview]
Message-ID: <20141020094252.14456.58891.stgit@gklab-18-011.igk.intel.com> (raw)

From: Miroslaw Walukiewicz <miroslaw.walukiewicz@intel.com>

Add new  PKT_TX_TCP_SEG flag
Add new fields in the tx offload fields indicating MSS and L4 len

Signed-off-by: Mirek Walukiewicz <miroslaw.walukiewicz@intel.com>
---
 lib/librte_mbuf/rte_mbuf.h |   23 ++++++++++++++++++-----
 1 file changed, 18 insertions(+), 5 deletions(-)

diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
index ddadc21..bcb09b9 100644
--- a/lib/librte_mbuf/rte_mbuf.h
+++ b/lib/librte_mbuf/rte_mbuf.h
@@ -114,6 +114,9 @@ extern "C" {
 /* Bit 51 - IEEE1588*/
 #define PKT_TX_IEEE1588_TMST (1ULL << 51) /**< TX IEEE1588 packet to timestamp. */
 
+/* Bit 49 - TCP transmit segmenation offload */
+#define PKT_TX_TCP_SEG (1ULL << 49) /**< TX TSO offload */
+ 
 /* Use final bit of flags to indicate a control mbuf */
 #define CTRL_MBUF_FLAG       (1ULL << 63) /**< Mbuf contains control data */
 
@@ -189,12 +192,22 @@ struct rte_mbuf {
 	struct rte_mbuf *next;    /**< Next segment of scattered packet. */
 
 	/* fields to support TX offloads */
-	union {
-		uint16_t l2_l3_len; /**< combined l2/l3 lengths as single var */
-		struct {
-			uint16_t l3_len:9;      /**< L3 (IP) Header Length. */
-			uint16_t l2_len:7;      /**< L2 (MAC) Header Length. */
+	/* two bytes - l2/l3 len for compatibility (endian issues)
+	 * two bytes - reseved for alignment
+	 * two bytes - l4 len (TCP/UDP) header len
+	 * two bytes - TCP tso segment size 
+ 	 */
+	struct {
+		union {
+			uint16_t l2_l3_len; /**< combined l2/l3 len */
+			struct {
+				uint16_t l3_len:9; /**< L3 (IP) Header */
+				uint16_t l2_len:7; /**< L2 (MAC) Header */
+			};
 		};
+		uint16_t reserved_tx_offload;
+		uint16_t l4_len;            /**< TCP/UDP header len */
+		uint16_t tso_segsz;         /**< TCP TSO segment size */
 	};
 } __rte_cache_aligned;
 

             reply	other threads:[~2014-10-20  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  9:42 miroslaw.walukiewicz [this message]
2014-10-20 11:30 ` Thomas Monjalon
2014-10-20 12:45   ` Walukiewicz, Miroslaw
2014-10-20 13:51     ` Thomas Monjalon
2014-10-20 14:03       ` Walukiewicz, Miroslaw

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=20141020094252.14456.58891.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).