From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: nickpiggin@yahoo.com.au, davej@redhat.com, arjan@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 7/8] badpage: ratelimit print_bad_pte and bad_page
Date: Wed, 3 Dec 2008 13:04:17 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0812031253060.6817@blonde.anvils> (raw)
In-Reply-To: <20081202165654.b84ffdad.akpm@linux-foundation.org>
On Tue, 2 Dec 2008, Andrew Morton wrote:
> On Mon, 1 Dec 2008 00:46:53 +0000 (GMT)
> Hugh Dickins <hugh@veritas.com> wrote:
> > + /*
> > + * Allow a burst of 60 reports, then keep quiet for that minute;
> > + * or allow a steady drip of one report per second.
> > + */
> > + if (nr_shown == 60) {
> > + if (time_before(jiffies, resume)) {
> > + nr_unshown++;
> > + goto out;
> > + }
> > + if (nr_unshown) {
> > + printk(KERN_EMERG
> > + "Bad page state: %lu messages suppressed\n",
> > + nr_unshown);
> > + nr_unshown = 0;
> > + }
> > + nr_shown = 0;
> > + }
> > + if (nr_shown++ == 0)
> > + resume = jiffies + 60 * HZ;
> > +
>
> gee, that's pretty elaborate. There's no way of using the
> possibly-enhanced ratelimit.h?
Thanks a lot for the pointer: I'd browsed around kernel/printk.c and
not found what I needed, hadn't realized there's a lib/ratelimit.c.
It looks eerily like what I'm trying to do, just a less specific
missed/suppressed message, never mind that. I'll try making a patch
later to replace this (in its subsequent KERN_ALERT form) by that -
in doing so, perhaps I'll encounter a problem, but should be good.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-03 13:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 0:37 [PATCH 0/8] badpage: more resilient bad page pte and rmap Hugh Dickins
2008-12-01 0:40 ` [PATCH 1/8] badpage: simplify page_alloc flag check+clear Hugh Dickins
2008-12-01 14:47 ` Christoph Lameter
2008-12-01 23:50 ` Hugh Dickins
2008-12-02 2:21 ` Christoph Lameter
2008-12-02 10:39 ` Hugh Dickins
2008-12-02 13:12 ` Christoph Lameter
2008-12-02 14:12 ` Hugh Dickins
2008-12-03 0:57 ` Andrew Morton
2008-12-01 0:41 ` [PATCH 2/8] badpage: keep any bad page out of circulation Hugh Dickins
2008-12-01 14:49 ` Christoph Lameter
2008-12-01 23:19 ` Hugh Dickins
2008-12-01 0:42 ` [PATCH 3/8] badpage: replace page_remove_rmap Eeek and BUG Hugh Dickins
2008-12-01 0:43 ` [PATCH 4/8] badpage: vm_normal_page use print_bad_pte Hugh Dickins
2008-12-01 0:44 ` [PATCH 5/8] badpage: zap print_bad_pte on swap and file Hugh Dickins
2008-12-01 0:45 ` [PATCH 6/8] badpage: remove vma from page_remove_rmap Hugh Dickins
2008-12-01 0:46 ` [PATCH 7/8] badpage: ratelimit print_bad_pte and bad_page Hugh Dickins
2008-12-03 0:56 ` Andrew Morton
2008-12-03 13:04 ` Hugh Dickins [this message]
2008-12-01 0:48 ` [PATCH 8/8] badpage: KERN_ALERT BUG instead of KERN_EMERG Hugh Dickins
2008-12-01 14:40 ` Christoph Lameter
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=Pine.LNX.4.64.0812031253060.6817@blonde.anvils \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox