From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: pvvvarma@techmas.hcltech.com (Vasu Varma P V)
Cc: linux-kernel@vger.kernel.org (kernel Linux)
Subject: Re: scheduling in kmalloc()
Date: Fri, 6 Jul 2001 16:03:52 +0100 (BST) [thread overview]
Message-ID: <E15IX97-0004Uc-00@the-village.bc.nu> (raw)
In-Reply-To: <3B45A7C1.7E684A7@techmas.hcltech.com> from "Vasu Varma P V" at Jul 06, 2001 05:27:53 PM
> if we use any thing other than GFP_ATOMIC, does it result in scheduling
> out the process if there is no memory available?
> with GFP_KERNRL, I think we try freeing pages to service the current
> request.
> or is there any possibility of kmalloc() failing even with GFP_KERNEL?
kmalloc can always fail, looping on a kmalloc at high level can almost always
cause deadlocks so you need to be prepared to fail
prev parent reply other threads:[~2001-07-06 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 11:57 Vasu Varma P V
2001-07-06 15:03 ` Alan Cox [this message]
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=E15IX97-0004Uc-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pvvvarma@techmas.hcltech.com \
/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®