From: Benjamin LaHaise <bcrl@redhat.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: mingo@redhat.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] silence an unnescessary raid5 debugging message
Date: Tue, 8 Oct 2002 19:36:12 -0400 [thread overview]
Message-ID: <20021008193612.H15858@redhat.com> (raw)
In-Reply-To: <15779.27330.284336.914423@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Wed, Oct 09, 2002 at 09:31:14AM +1000
On Wed, Oct 09, 2002 at 09:31:14AM +1000, Neil Brown wrote:
> This is there as a 'printk' deliberately. It warns you that what you
> are doing isn't really supported and will cause a substantial
> performance hit (as all IO to the array is completely serialised
> around one of these messages).
As it stands, the syslogging from the printk does more damage to performance
than the underlying problem. Besides, LVM snapshots are slow, but they're
useful for a class of problems anyways.
-ben
next prev parent reply other threads:[~2002-10-08 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 22:03 [patch] silence an unnescessary raid5 debugging message Benjamin LaHaise
2002-10-08 23:31 ` Neil Brown
2002-10-08 23:36 ` Benjamin LaHaise [this message]
2002-10-09 0:51 ` David S. Miller
2002-10-09 1:02 ` Benjamin LaHaise
2002-10-09 11:55 ` jw schultz
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 17:36 David Mansfield
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=20021008193612.H15858@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.