On Thu, Feb 6, 2020 at 7:44 PM Thomas Monjalon <tho...@monjalon.net> wrote: > > 21/01/2020 09:00, jer...@marvell.com: > > From: Jerin Jacob <jer...@marvell.com> > > > > Some machines may have a lot of PCI devices, logs from PCI probe > > creates a lot of clutter on boot-up, typically one needs > > to scroll the screen to find other issues in boot-up. > > > > This patch changes the loglevel of PCI probes to `debug` > > to reduce the clutter on default boot-up logs > > I think the PCI probe informations are... informational. > Maybe you are just not interested in info logs. > If this is the case, I suggest to change the log level at runtime.
I am wondering, what would be the right balance, Following is DPDK startup output from octeontx2[1] It creates a lot of clutter in the "default" boot up. Why not enable below prints using log level at runtime? I believe it comes as a debug category, i.e information required to debug if something is not working, dpdk bind script already lists what is bound to DPDK. Suggestion to remove clutter? [1] EAL: Detected 24 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: No available hugepages reported in hugepages-2048kB EAL: Probing VFIO support... EAL: VFIO support initialized EAL: PCI device 0002:01:00.1 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:00.2 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:00.3 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:00.4 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:00.5 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:00.6 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:00.7 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.0 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.1 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.2 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.3 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.4 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.5 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.6 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:01.7 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:01:02.0 on NUMA socket 0 EAL: probe driver: 177d:a0f8 net_octeontx2 EAL: PCI device 0002:02:00.0 on NUMA socket 0 EAL: probe driver: 177d:a063 net_octeontx2 EAL: using IOMMU type 1 (Type 1) EAL: PCI device 0002:03:00.0 on NUMA socket 0 EAL: probe driver: 177d:a063 net_octeontx2 EAL: PCI device 0002:04:00.0 on NUMA socket 0 EAL: probe driver: 177d:a063 net_octeontx2 EAL: PCI device 0002:05:00.0 on NUMA socket 0 EAL: probe driver: 177d:a063 net_octeontx2 EAL: PCI device 0002:06:00.0 on NUMA socket 0 EAL: probe driver: 177d:a063 net_octeontx2 EAL: PCI device 0002:07:00.0 on NUMA socket 0 EAL: probe driver: 177d:a063 net_octeontx2 EAL: PCI device 0002:08:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0f9 event_octeontx2 EAL: PCI device 0002:09:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0f9 event_octeontx2 EAL: PCI device 0002:0a:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0f9 event_octeontx2 EAL: PCI device 0002:0b:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0f9 event_octeontx2 EAL: PCI device 0002:0c:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0fb mempool_octeontx2 EAL: PCI device 0002:0d:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0fb mempool_octeontx2 EAL: PCI device 0002:0e:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0f9 event_octeontx2 EAL: PCI device 0002:0f:00.0 on NUMA socket 0 EAL: probe driver: 177d:a0fb mempool_octeontx2 APP: HPET is not enabled, using TSC as default timer > > >
