[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <18454.41142.654638.785292@notabene.brown>
Date: Tue, 29 Apr 2008 14:14:46 +1000
From: Neil Brown <neilb@...e.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
Bernd Schubert <bernd-schubert@....de>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH 008 of 9] md: md: raid5 rate limit error printk
On Monday April 28, akpm@...ux-foundation.org wrote:
> On Tue, 29 Apr 2008 13:35:34 +1000 NeilBrown <neilb@...e.de> wrote:
>
> > + printk_rl(KERN_WARNING "raid5:%s: read error NOT corrected!! "
> > + "(sector %llu on %s).\n",
> > + mdname(conf->mddev),
> > + (unsigned long long)(sh->sector + rdev->data_offset),
> > + bdn);
> > else if (atomic_read(&rdev->read_errors)
> > > conf->max_nr_stripes)
> > printk(KERN_WARNING
> >
> > diff .prev/include/linux/raid/md_k.h ./include/linux/raid/md_k.h
> > --- .prev/include/linux/raid/md_k.h 2008-04-29 12:25:24.000000000 +1000
> > +++ ./include/linux/raid/md_k.h 2008-04-29 12:27:58.000000000 +1000
> > @@ -368,6 +368,9 @@ static inline void safe_put_page(struct
> > if (p) put_page(p);
> > }
> >
> > +#define printk_rl printk_ratelimit() ?: printk
>
> (boggle)
You don't like the "?:" operator?
Maybe
printk_ratelimit() && printk
?
>
> Isn't this backwards? Should be !printk_ratelimit()?
Arggg.. Did I do that? Bother.
>
> open-coding the printk_ratelimit() at each callsite would be more
> conventional.
True, but it can get noisy, adding an extra level of indent where it
isn't really needed (and the printk lines tend to be fairly long
already).
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists