From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw116050 [PATCH] [v2, 3/5] lib: move mbuf next pointer to first cache line
Date: Wed, 7 Sep 2022 14:11:27 -0400 (EDT) [thread overview]
Message-ID: <20220907181127.A01876D509@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/116050
_apply patch failure_
Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Wednesday, September 07 2022 13:43:38
Applied on: CommitID:4aee6110bb10b0225fa9562f2e48af233a9058a1
Apply patch set 116050 failed:
Checking patch lib/mbuf/rte_mbuf_core.h...
error: while searching for:
* working on vector drivers easier.
*/
rte_iova_t buf_iova __rte_aligned(sizeof(rte_iova_t));
/**
* Reserved for dynamic field in builds where physical address
* field is invalid.
*/
uint64_t dynfield2;
};
/* next 8 bytes are initialised on RX descriptor rearm */
error: patch failed: lib/mbuf/rte_mbuf_core.h:590
Hunk #2 succeeded at 701 (offset -13 lines).
Checking patch lib/meson.build...
Applying patch lib/mbuf/rte_mbuf_core.h with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
Applied patch lib/meson.build cleanly.
diff a/lib/mbuf/rte_mbuf_core.h b/lib/mbuf/rte_mbuf_core.h (rejected hunks)
@@ -590,11 +590,14 @@ struct rte_mbuf {
* working on vector drivers easier.
*/
rte_iova_t buf_iova __rte_aligned(sizeof(rte_iova_t));
+#if RTE_IOVA_AS_VA
/**
- * Reserved for dynamic field in builds where physical address
- * field is invalid.
+ * Next segment of scattered packet.
+ * This field is valid when physical address field is invalid.
+ * Otherwise next pointer in the second cache line will be used.
*/
- uint64_t dynfield2;
+ struct rte_mbuf *next;
+#endif
};
/* next 8 bytes are initialised on RX descriptor rearm */
https://lab.dpdk.org/results/dashboard/patchsets/23446/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-09-07 18:11 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=20220907181127.A01876D509@noxus.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).