On Mon, May 18, 2015 at 6:39 PM, Stephen Hemminger < stephen at networkplumber.org> wrote:
> On Mon, 18 May 2015 10:32:01 +0100 > Bruce Richardson <bruce.richardson at intel.com> wrote: > > > For the most part, this looks fine. However, I'm unsure about changing > the log > > level of the messages stating what the RX and TX burst functions in use > are. I > > would view this as important information that should generally be > displayed as > > the performance impacts of using a sub-optimal RX/TX code path are large. > > > > /Bruce > > > At INFO level it shows up in log files that customers read. > This is an issue where DPDK has to grow up and be ready for real world > use, rather than being developer friendly. > > Our customers ask about every log message (believe me). So if there > is no problem the drivers must be absolutely silent (STFU) > Are there messages at INFO level you want to keep ? Or can't you just set the log level (the runtime option not the build one) to something like WARNING or ERR ? -- David Marchand
