[dpdk-dev] Too much print of testpmd

Lu, Wenzhuo wenzhuo.lu at intel.com
Wed Apr 26 07:10:44 CEST 2017


Hi Gaetan,
When using DPDK PF + DPDK VF, there's too much print like,
Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Port 0: VF Mbox event

Make it a little hard to type a CLI.
I think it's introduced by this commit,
commit 76ad4a2d82d4d72c3a7ed4675d77268b5fae3cc9
Author: Gaetan Rivet <gaetan.rivet at 6wind.com>
Date:   Tue Apr 18 14:17:40 2017 +0200

    app/testpmd: add generic event handler

    This is a rather simple handler that prints a message with the name of
    the current event. It can be used to check PMD callback registration and
triggers.

Seems it's not good to print every event directly. If it's necessary, is it better to redirect the output to a log file?
Thanks.


Best regards
Wenzhuo Lu



More information about the dev mailing list