mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: erblichs <erblichs@earthlink.net>
To: linux-kernel@vger.kernel.org
Cc: erblichs@earthlink.net
Subject: RFE: __alloc_pages() SLAB_PANIC & gfp_mask
Date: Fri, 22 Feb 2008 17:07:06 -0800 (GMT-08:00)	[thread overview]
Message-ID: <9643105.1203728826946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net> (raw)

Group,


           Currrently I do not subscribe to this mail alias, so please
           keep the cc.

           Currently a few calls exist where WAIT is specified (
           (GFP_KERNEL)for the slab/slob allocators and also as an
           additional argument, SLAB_PANIC is checked against the
           return of the request for memory allocation. SLAB_PANIC
           is not passed to __alloc_pages() as part of the gfp_mask.

           If the memory allocation fails, and the flag is turned
           on, then a panic will ensure.. There is a very simple fix
           for this. The assumption is too basicly ASSERT a guarantee
           that memory failure in this case will not occur.

           The suggestion is to add the SLAB_PANIC arg to the gfp_mask,
           add it to the mask in the SLAB/SLUB callers,
           and have that checked within __alloc_pages 
           if a mem alloc failure is about to occur 
           after the check for no WAITers.

           If it is set, then force additional loops within the function.

           This would remove new cache creates from causing a panic when
           a low memory condition exists.

           Mitchell Erblich

                 reply	other threads:[~2008-02-23  1:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9643105.1203728826946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net \
    --to=erblichs@earthlink.net \
    --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

all inboxes | Powered by JetHome®