On 1/25/2018 5:00 PM, Andrew Rybchenko wrote: > Unfortunately we're a bit late with dynamic logging implementation. > So, it can wait for 18.05 release cycle if required. > > The series adds EXPERIMENTAL EAL feature which removes dependency > on EAL arguments processing and log types registration. It stores > EAL loglevel arguments in the list and adds API function to register > a new log type and pick up its value from EAL arguments. > > For us it is important since we would like to be able to control > per-device log level, e.g. pmd.net.sfc.main.0000:01:00.0.
It is good idea to have device level granularity in logging, I believe other devices also would like have this, if only there would be an easy way to apply this capability to all PMDs. > > The series already follows log type names format defined recently. > > Ivan Malov (6): > eal: register log type and pick level from EAL args > net/sfc: add support for driver-wide dynamic logging > net/sfc: add support for per-port dynamic logging > net/sfc: prepare to merge init logs with main log type > net/sfc: remove dedicated init log parameter > net/sfc: add dynamic log level for MCDI messages <...>
