On 10/05/2012 09:14 AM, Joe Perches wrote:
On Fri, 2012-10-05 at 08:55 -0500, Nathan Zimmer wrote:
On 10/04/2012 11:37 AM, Joe Perches wrote:
On Thu, 2012-10-04 at 11:02 -0500, Nathan Zimmer wrote:
At many of our customer sites the log level is set to KERN_DEBUG. It
helps avoid reboots due to operator impatience. Machines this large
take significantly longer then typical to boot and seeing the extra
messages reassures them that the kernel isn't hung.
That argues for adding some KERN_INFO "still booting" messages
not logging unnecessary KERN_DEBUG messages.
Actually I would think that argues for reducing boot times on these
large systems.
Right.
That's an independent argument, but sure, go ahead
and do that too.
Here is output for my workstation a simple 4x box
-bash-4.1$ dmesg | grep "type [0-9][0-9] class" | wc
12 108 804
-bash-4.1$ dmesg | wc
744 6359 49474
Here is some output from one of the biggest boxes.
-bash-4.1$ dmesg | wc
26503 235414 1811651
-bash-4.1$ dmesg | grep "type [0-9][0-9] class" | wc
12085 108765 821780
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
