[lkml]   [2004]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Suspend 2 merge: 14/51: Disable page alloc failure message when suspending

On Fri, 2004-11-26 at 08:56, Pavel Machek wrote:
> Hi!
> > > > While eating memory, we will potentially trigger this a lot. We
> > > > therefore disable the message when suspending.
> > >
> > > You should only trigger this while eating memory, so *one* GFP_NOWARN should be
> > > enough. And shrink_all_memory should fix it anyway.
> >
> > Agreed. I wasn't seriously suggesting changing everywhere to be
> > GFP_NOWARN. Perhaps I should be more explicit in what I'm saying here.
> > The problem isn't just suspend trying to allocate memory. It's
> > _ANYTHING_ that might be running trying to allocate memory while we're
> > eating memory. (Remember that we don't just call shrink_all_memory, but
> > also allocate that memory so other processes don't grab it and stop us
> > making forward progress). As a result, they're going to scream when they
> > can't allocate a page.
> Hmm, that does not look too healthy. That means that userland programs
> will see all kinds of weird error conditions that normally
> "almost-can't-happen" during normal usage.

Failure to allocate memory should be something any caller to get_*_page
deals with, so if they don't, are we to be blamed?


Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901

You see, at just the right time, when we were still powerless, Christ
died for the ungodly. -- Romans 5:6

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:08    [W:0.205 / U:64.608 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site