> In an effort to get greater control over which printk()'s are logged
> during boot and after, I've put together this patch that introduces the
> concept of printk subsystems. The problem that some are beginning to
> face with larger machines is that certain subsystems are overly verbose
> (SCSI, USB, cpu related messages on large NUMA or SMP machines)
> and they overflow the buffer. Making the logbuffer bigger is a stop gap
> solution but I think this is a more elegant solution.
> Basically, each printk is assigned to a subsystem and that subsystem has
> the same set of values that the console_printk array has. The
> difference is that the console_printk loglevel decides if the message
> goes to the console whereas the subsystem loglevel decides if that
> message goes to the log at all.
Well, I consider this stop gap too... Right solution is to kill
printk()s from too verbose part so that it does not overflow....
Pavel
-- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/