public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] remove unimplemented syscalls noise
Date: Wed, 19 Nov 2003 20:33:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106927403504014@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106926030617023@msgid-missing>

>>>>> On Wed, 19 Nov 2003 20:20:20 +0000, Matthew Wilcox <willy@debian.org> said:

  >>  And yet both features are incredibly useful when debugging,
  >> something you seem to ignore.

  Matthew> No, it *isn't*.  The majority of systems in use are not
  Matthew> being debugged (regardless of how you & I spend most of our
  Matthew> time).

Please read my sentence: it's incredibly useful when _debugging_ a
problem.

Nobody suggests to print those messages for normal users.  dmesg -n4
will take care of them for good.

  Matthew> Every time we emit something to the system log, it's a
  Matthew> potential support call.  Our friends in other parts of HP
  Matthew> are already unhappy with how much output Linux produces
  Matthew> even when everything's OK.  It's also a sysadmin hassle as
  Matthew> logfiles fill up more quickly when this kind of junk goes
  Matthew> by.

Can I say dmesg -n4??

  Matthew> I'm sure this was useful for debugging once, but those days
  Matthew> are gone.  We need to print less of this stuff.  Something
  Matthew> a lot of places do is:

  Matthew> #undef DEBUG

  Matthew> #ifdef DEBUG #define DBG(x...) printk(x) #else #define
  Matthew> DBG(x...)  #endif

  Matthew> Would it mollify you if these printks were turned into
  Matthew> DBGs?

Nope.  dmesg -n4 is adequate.

	--david

  parent reply	other threads:[~2003-11-19 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 16:42 [PATCH] remove unimplemented syscalls noise Kyle McMartin
2003-11-19 19:44 ` David Mosberger
2003-11-19 19:54 ` Matthew Wilcox
2003-11-19 20:11 ` David Mosberger
2003-11-19 20:15 ` Seth, Rohit
2003-11-19 20:20 ` Matthew Wilcox
2003-11-19 20:20 ` David Mosberger
2003-11-19 20:33 ` David Mosberger [this message]
2003-11-19 20:35 ` Matthew Wilcox
2003-11-19 21:13 ` Rich Altmaier
2003-11-19 21:21 ` David Mosberger
2003-11-19 21:31 ` David Mosberger
2003-11-19 23:13 ` Matthias Fouquet-Lapar

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=marc-linux-ia64-106927403504014@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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