Re: swapper: page allocation failure. order:3, mode:0x20

From: Andrew Morton
Date: Thu Jan 01 2004 - 05:26:45 EST


Anton Blanchard <anton@xxxxxxxxx> wrote:
>
> > swapper: page allocation failure. order:3, mode:0x20
>
> ...
> We should probably rate limit that printk. Andrew: I was thinking of
> stealing net_ratelimit and calling it core_ratelimit or whatever. Then
> wrap these non critical things with it. Overkill?

Actually my intent was just to remove it (and __GFP_NOWARN) - it's just
development-time debug. But it is handy on occasion.

So sure, ratelimit it, make it KERN_INFO and maybe add a dump_stack()?

(printk_ratelimit() may be a suitable name)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/