On 7/13/20 10:06 AM, David Marchand wrote: > Enabling debug logs in dpdk can be a challenge to be sure of what is > actually enabled, add commands to list and change those log levels. > However, these commands do not help when tracking issues in dpdk init > itself: dump log levels right after init. > > Example: > $ ovs-appctl dpdk/log-list > global log level is debug > id 0: lib.eal, level is info > id 1: lib.malloc, level is info > id 2: lib.ring, level is info > id 3: lib.mempool, level is info > id 4: lib.timer, level is info > id 5: pmd, level is info > [...] > id 37: pmd.net.bnxt.driver, level is notice > id 38: pmd.net.e1000.init, level is notice > id 39: pmd.net.e1000.driver, level is notice > id 40: pmd.net.enic, level is info > [...] > > $ ovs-appctl dpdk/log-set debug pmd.*:notice > $ ovs-appctl dpdk/log-list > global log level is debug > id 0: lib.eal, level is debug > id 1: lib.malloc, level is debug > id 2: lib.ring, level is debug > id 3: lib.mempool, level is debug > id 4: lib.timer, level is debug > id 5: pmd, level is debug > [...] > id 37: pmd.net.bnxt.driver, level is notice > id 38: pmd.net.e1000.init, level is notice > id 39: pmd.net.e1000.driver, level is notice > id 40: pmd.net.enic, level is notice > [...] > > Signed-off-by: David Marchand <david.march...@redhat.com> > --- > Changes since v1: > - added a NEWS entry, > - added a man section for DPDK commands, > - other comments, >
Applied. Thanks! Best regards, Ilya Maximets. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
