public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Martin Hicks <mort@bork.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Generic way to control display of debug printk's
Date: Tue, 25 Mar 2003 13:38:29 -0800	[thread overview]
Message-ID: <3E80CC55.6010007@zytor.com> (raw)
In-Reply-To: <20030325192843.GB11198@bork.org>

Martin Hicks wrote:
> 
> Okay, perhaps I didn't clearly identify the problem last time.  The
> problem is the number of messages that go into the log_buf.  On
> large systems we can certainly just crank up the size of log_buf, but I
> don't see this as a terribly elegant solution.
> 
> I think there should be some facility, mirroring the way we can set a
> threshold for console messages, to decide if a message is logged at all.
> For example, setting console_loglevel and log_loglevel (the new
> threshold) to 7 results in no KERN_DEBUG messages begin printed to the
> console or the log.
> 
> I'm testing a patch now, but are there any comments on the basic idea?
> Is it preferrable to just crank up the size of log_buf?
> 

This is probably a good idea.  It might also be worthwhile to implement
per-subsystem filtering similar to what syslog has; the network
subsystem is particular is notoriously noisy when it comes to telling me
that someone else sent bad packets.  If you're a public Internet server,
that happens *all the time*...

	-hpa



      reply	other threads:[~2003-03-25 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 22:37 [patch] Generic way to control display of debug printk's Martin Hicks
2003-03-22  2:15 ` H. Peter Anvin
2003-03-25 19:28   ` Martin Hicks
2003-03-25 21:38     ` H. Peter Anvin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E80CC55.6010007@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mort@bork.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox