From: Li Feng <fengli@smartx.com>
Cc: dev@dpdk.org, lifeng1519@gmail.com, Li Feng <fengli@smartx.com>
Subject: [dpdk-dev] [PATCH v2] log: support custom log function
Date: Sat, 6 Feb 2021 01:42:04 +0800 [thread overview]
Message-ID: <20210205174204.1878089-1-fengli@smartx.com> (raw)
In-Reply-To: <20210205112433.1681853-1-fengli@smartx.com>
Currently, the dpdk log is out to stdout/stderr and syslog.
The rte_openlog_stream could set an external FILE* stream, but it asks the
consumer to give it a FILE* pointer.
For C++ or other languages, it's hard to get a libc FILE*.
Support to set a hook method is another choice for this scenario.
Change-Id: I3b2419cc2fe5256205daa8077fd8862a8e58fb6c
Signed-off-by: Li Feng <fengli@smartx.com>
---
v2: simplify the code.
lib/librte_eal/include/rte_eal.h | 16 ++++++++++++++++
lib/librte_eal/linux/eal_log.c | 10 ++++++++++
2 files changed, 26 insertions(+)
diff --git a/lib/librte_eal/include/rte_eal.h b/lib/librte_eal/include/rte_eal.h
index eaf6469e5..bd6cf554b 100644
--- a/lib/librte_eal/include/rte_eal.h
+++ b/lib/librte_eal/include/rte_eal.h
@@ -501,6 +501,22 @@ rte_eal_mbuf_user_pool_ops(void);
const char *
rte_eal_get_runtime_dir(void);
+/**
+ * Usage function typedef used by the application usage function.
+ *
+ * Use this function typedef to define a logger formatter.
+ */
+typedef cookie_write_function_t rte_log_func_t;
+
+/**
+ * Set a customized logger.
+ *
+ * @param logf
+ * The customized logger function.
+ */
+void
+rte_eal_set_log_func(rte_log_func_t *logf);
+
#ifdef __cplusplus
}
#endif
diff --git a/lib/librte_eal/linux/eal_log.c b/lib/librte_eal/linux/eal_log.c
index 43c8460bf..c0a7a12ab 100644
--- a/lib/librte_eal/linux/eal_log.c
+++ b/lib/librte_eal/linux/eal_log.c
@@ -60,3 +60,13 @@ rte_eal_log_init(const char *id, int facility)
return 0;
}
+
+/*
+ * Set the customized logger, it will override the default action, which is
+ * writing to syslog and stdout.
+ */
+void
+rte_eal_set_log_func(rte_log_func_t *logf)
+{
+ console_log_func.write = logf;
+}
--
2.29.2
next prev parent reply other threads:[~2021-02-05 17:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 11:24 [dpdk-dev] [PATCH] " Li Feng
2021-02-05 11:31 ` Feng Li
2021-02-05 11:55 ` David Marchand
2021-02-05 12:22 ` Feng Li
2021-02-05 14:08 ` Dmitry Kozlyuk
2021-02-05 16:39 ` Stephen Hemminger
2021-02-05 16:10 ` Stephen Hemminger
2021-02-05 16:54 ` Feng Li
2021-02-05 17:06 ` Feng Li
2021-02-05 17:42 ` Li Feng [this message]
2021-02-05 17:47 ` [dpdk-dev] [PATCH v2] " Feng Li
2021-02-05 19:32 ` Dmitry Kozlyuk
2021-02-08 6:58 ` Feng Li
2021-02-08 22:40 ` Dmitry Kozlyuk
2021-02-10 3:59 ` Feng Li
2021-02-10 5:20 ` [dpdk-dev] [PATCH v3] " Li Feng
2021-02-18 2:55 ` Feng Li
2023-06-15 16:12 ` Stephen Hemminger
2021-02-18 6:12 ` [dpdk-dev] [PATCH v4] " Li Feng
2021-02-19 8:11 ` Dmitry Kozlyuk
2021-02-23 11:22 ` Feng Li
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=20210205174204.1878089-1-fengli@smartx.com \
--to=fengli@smartx.com \
--cc=dev@dpdk.org \
--cc=lifeng1519@gmail.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).