Messages in this thread | | | Subject | Re: [patch] printk subsystems | From | Jes Sorensen <> | Date | 08 Apr 2003 18:00:49 -0400 |
| |
>>>>> "Pavel" == Pavel Machek <pavel@ucw.cz> writes:
Pavel> Hi! >> Killing the printk's means they are not around if you have an end >> user who is running into problems at boot time. Having a feature >> like this means they can default to 'off' then if a problem arises, >> whoever is doing the support can ask the user to try and enable >> printk's for say SCSI and get the input, without haven to rebuild >> the kernel from scratch.
Pavel> Well, I think we should first kill all crappy messages -- that Pavel> benefits everyone. I believe that if we kill all unneccessary Pavel> (carrying no information except perhaps copyright or Pavel> advertising) will help current problem a lot.
I agree that some messages can be eliminated, but not all of them. Even some of the ones you suggested might be valuable to keep, like the CPU flags. Generally this isn't a problem on a small box with 2 CPUs and 2 disks, but if you have 32 CPUs and 64 SCSI disks, the amount of data being printed becomes quite substantial.
So while I agree that it wouldn't hurt for us to eliminate some unncessary printk's, then I still think Martin's patch has a lot of merit.
Cheers, Jes - 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/
| |