On Mon, 4 Jul 2005, Anton Blanchard wrote:
>
> Hi,
>
> > Why not just remove the printk's when DEBUG_KERNEL is off. The problem
> > that I've found is that the latency in the system sky rockets when OOM
> > triggers. It's due to the excessive printk usage.
> >
> > I'm sure it's not ifdef'ed for a reason , but it would be nice to have an
> > easy way to silence it.
>
> We've had customer situations where that information would have been
> very useful. Also DEBUG_KERNEL is enabled on some distros so it wouldnt
> help there.
>
> Id suggest adding a printk level to the printks in mm/oom-kill.c and
> using /proc/sys/kernel/printk to silence them.
The latency problem stems from running printk, so I'm not sure that
silencing them in this way would help . We could add a debug option just
for this ? I'm sure OOM has other debugging output . CONFIG_OOM, and
CONFIG_DEBUG_OOM .
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |