From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw104701 [PATCH] examples/ipsec-secgw: wrong offload flag used for TSO IPv6
Date: Thu, 25 Nov 2021 13:48:11 +0000 (UTC) [thread overview]
Message-ID: <20211125134811.9212F6056D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/104701
_apply patch failure_
Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Thursday, November 25 2021 13:03:54
Applied on: CommitID:872c6a28075ccae66a31affef7ae3c5e9811affc
Apply patch set 104701 failed:
Checking patch examples/ipsec-secgw/ipsec_process.c...
error: while searching for:
mb[j]->outer_l3_len = mb[j]->l3_len;
mb[j]->outer_l2_len = mb[j]->l2_len;
mb[j]->ol_flags |=
(RTE_MBUF_F_TX_OUTER_IP_CKSUM |
RTE_MBUF_F_TX_TUNNEL_ESP);
}
mb[j]->l4_len = sizeof(struct rte_tcp_hdr);
mb[j]->ol_flags |= (RTE_MBUF_F_TX_TCP_SEG |
error: patch failed: examples/ipsec-secgw/ipsec_process.c:232
Applying patch examples/ipsec-secgw/ipsec_process.c with 1 reject...
Rejected hunk #1.
diff a/examples/ipsec-secgw/ipsec_process.c b/examples/ipsec-secgw/ipsec_process.c (rejected hunks)
@@ -232,8 +232,10 @@ prep_process_group(void *sa, struct rte_mbuf *mb[], uint32_t cnt)
mb[j]->outer_l3_len = mb[j]->l3_len;
mb[j]->outer_l2_len = mb[j]->l2_len;
mb[j]->ol_flags |=
- (RTE_MBUF_F_TX_OUTER_IP_CKSUM |
- RTE_MBUF_F_TX_TUNNEL_ESP);
+ RTE_MBUF_F_TX_TUNNEL_ESP;
+ if (RTE_ETH_IS_IPV4_HDR(ptype))
+ mb[j]->ol_flags |=
+ RTE_MBUF_F_TX_OUTER_IP_CKSUM;
}
mb[j]->l4_len = sizeof(struct rte_tcp_hdr);
mb[j]->ol_flags |= (RTE_MBUF_F_TX_TCP_SEG |
https://lab.dpdk.org/results/dashboard/patchsets/20378/
UNH-IOL DPDK Community Lab
reply other threads:[~2021-11-25 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211125134811.9212F6056D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).