From: Jianfeng Tan <jianfeng.tan@intel.com>
To: dev@dpdk.org
Cc: konstantin.ananyev@intel.com, jingjing.wu@intel.com,
mark.b.kavanagh@intel.com, Jianfeng Tan <jianfeng.tan@intel.com>
Subject: [PATCH 1/2] examples/tep_term: fix offload on VXLAN failure
Date: Thu, 4 Aug 2016 07:58:48 +0000 [thread overview]
Message-ID: <1470297529-100773-2-git-send-email-jianfeng.tan@intel.com> (raw)
In-Reply-To: <1470297529-100773-1-git-send-email-jianfeng.tan@intel.com>
Based on previous fix of offload on VXLAN using i40e, applications
need to set proper tunneling type on ol_flags so that i40e driver
can pass it to NIC.
Fixes: a50245ede72a ("examples/tep_term: initialize VXLAN sample")
Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
---
examples/tep_termination/vxlan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/examples/tep_termination/vxlan.c b/examples/tep_termination/vxlan.c
index 5ee1f95..4bad33d 100644
--- a/examples/tep_termination/vxlan.c
+++ b/examples/tep_termination/vxlan.c
@@ -237,6 +237,8 @@ encapsulation(struct rte_mbuf *m, uint8_t queue_id)
m->outer_l2_len = sizeof(struct ether_hdr);
m->outer_l3_len = sizeof(struct ipv4_hdr);
+ ol_flags |= PKT_TX_TUNNEL_VXLAN;
+
m->ol_flags |= ol_flags;
m->tso_segsz = tx_offload.tso_segsz;
--
2.7.4
next prev parent reply other threads:[~2016-08-04 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 7:58 [PATCH 0/2] Two offloading issues of tep_term Jianfeng Tan
2016-08-04 7:58 ` Jianfeng Tan [this message]
2016-09-11 12:09 ` [PATCH 1/2] examples/tep_term: fix offload on VXLAN failure Yuanhan Liu
2016-09-12 8:42 ` Tan, Jianfeng
2016-09-12 9:36 ` Thomas Monjalon
2016-09-13 0:50 ` Tan, Jianfeng
2016-09-13 2:40 ` Yuanhan Liu
2016-08-04 7:58 ` [PATCH 2/2] examples/tep_term: fix inner L4 checksum failure Jianfeng Tan
2016-10-13 9:39 ` [PATCH 0/2] Two offloading issues of tep_term Thomas Monjalon
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=1470297529-100773-2-git-send-email-jianfeng.tan@intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mark.b.kavanagh@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 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.