* [dpdk-dev] don't use printf!
@ 2016-03-09 18:28 Stephen Hemminger
0 siblings, 0 replies; only message in thread
From: Stephen Hemminger @ 2016-03-09 18:28 UTC (permalink / raw)
To: dev
One thing I noticed while fixing mempool bug, was that there was a printf
in the library there. A reminder, code in DPDK library should never call printf
directly. printf in a real application is often ratholed off to /dev/null
and real output is through API's or syslog.
Offenders now:
rte_mempool
rte_acl
rte_cfgfile
I would fix rte_acl but it would require API breakage.
rte_acl_dump should take a FILE *
Some places have printf in debug path, which is less bad, but
still limits usage of DEBUG options
rte_sched
rte_timer
There are also several places in the BSD support, but I care less about those.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-03-09 18:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-09 18:28 [dpdk-dev] don't use printf! Stephen Hemminger
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).