Re: [dpdk-dev] [PATCH v3] log: support custom log function

On Wed, 10 Feb 2021 13:20:19 +0800 Li Feng wrote: > By default, 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*. > >

Re: [dpdk-dev] [PATCH v3] log: support custom log function

Ping…… Any comments about this? Thanks, On Wed, Feb 10, 2021 at 1:20 PM Li Feng wrote: > > By default, 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 languag

[dpdk-dev] [PATCH v3] log: support custom log function

By default, 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 is another choice for this scenario. Signed