public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Andrew Morton <akpm@osdl.org>
Cc: joneskoo@derbian.org, linux-kernel@vger.kernel.org
Subject: Re: swapper: page allocation failure. order:3, mode:0x20
Date: Fri, 2 Jan 2004 09:43:29 +1100	[thread overview]
Message-ID: <20040101224329.GO28023@krispykreme> (raw)
In-Reply-To: <20040101124504.69c80a14.akpm@osdl.org>

 
> This seems a bit odd.  It means that the further apart the message bursts
> are, the longer they are allowed to be.  Or something.
>
> Wouldn't it be better to say "after each greater-than-five second window,
> allow up to ten printk's as long as they happen in the next five
> milliseconds"?

Its 100% copied from the networking code. I would have thought we really
want that behaviour, if Im on a serial console I can only tolerate a
decent sized backtrace every few seconds. If I allow 10 bursts every 5
seconds then im screwed.

Instead we allow the burst of 10 once but then ratelimit it to one
per 5 seconds until we have had a long enough period of silence. The
main thing is that over the long term we have an average of one message
per 5 seconds.

Anton

  reply	other threads:[~2004-01-01 22:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01  9:35 swapper: page allocation failure. order:3, mode:0x20 Joonas Kortesalmi
2004-01-01 10:15 ` Anton Blanchard
2004-01-01 10:25   ` Andrew Morton
2004-01-01 13:01     ` Anton Blanchard
2004-01-01 20:45       ` Andrew Morton
2004-01-01 22:43         ` Anton Blanchard [this message]
2004-01-01 22:08       ` Christophe Saout
2004-01-01 22:45         ` Anton Blanchard
2004-01-01 23:13           ` Christophe Saout
2004-01-01 10:27   ` Anton Blanchard
2004-01-01 10:42     ` Arjan van de Ven

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=20040101224329.GO28023@krispykreme \
    --to=anton@samba.org \
    --cc=akpm@osdl.org \
    --cc=joneskoo@derbian.org \
    --cc=linux-kernel@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