From: Timothy McDaniel <timothy.mcdaniel@intel.com>
To: Jerin Jacob <jerinj@marvell.com>, Sunil Kumar Kori <skori@marvell.com>
Cc: dev@dpdk.org, erik.g.carrillo@intel.com, gage.eads@intel.com,
harry.van.haaren@intel.com
Subject: [dpdk-dev] [PATCH 1/1] eal: increase TRACE CTF SIZE to recommended size
Date: Mon, 5 Oct 2020 15:02:34 -0500 [thread overview]
Message-ID: <1601928154-26051-1-git-send-email-timothy.mcdaniel@intel.com> (raw)
Increase TRACE_CTF_FIELD_SIZE to 448, the recommended size.
Fixes "CTF field is too long" error when running with trace enabled.
Signed-off-by: Timothy McDaniel <timothy.mcdaniel@intel.com>
---
lib/librte_eal/common/eal_trace.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_eal/common/eal_trace.h b/lib/librte_eal/common/eal_trace.h
index 92c5951..438c2b7 100644
--- a/lib/librte_eal/common/eal_trace.h
+++ b/lib/librte_eal/common/eal_trace.h
@@ -24,7 +24,7 @@
#define TRACE_PREFIX_LEN 12
#define TRACE_DIR_STR_LEN (sizeof("YYYY-mm-dd-AM-HH-MM-SS") + TRACE_PREFIX_LEN)
-#define TRACE_CTF_FIELD_SIZE 384
+#define TRACE_CTF_FIELD_SIZE 448
#define TRACE_POINT_NAME_SIZE 64
#define TRACE_CTF_MAGIC 0xC1FC1FC1
#define TRACE_MAX_ARGS 32
--
2.6.4
next reply other threads:[~2020-10-05 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 20:02 Timothy McDaniel [this message]
2020-10-06 8:45 ` David Marchand
2020-10-06 9:22 ` [dpdk-dev] [EXT] " Sunil Kumar Kori
2020-10-06 9:39 ` David Marchand
2020-10-06 9:58 ` Jerin Jacob
2020-10-07 9:04 ` David Marchand
2020-10-07 10:07 ` Sunil Kumar Kori
2020-10-07 12:34 ` David Marchand
2020-10-08 7:33 ` [dpdk-dev] " David Marchand
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=1601928154-26051-1-git-send-email-timothy.mcdaniel@intel.com \
--to=timothy.mcdaniel@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.com \
--cc=skori@marvell.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 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).