From: Manfred Spraul <manfred@colorfullife.com>
To: "Peter T. Breuer" <ptb@it.uc3m.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can kfree sleep?
Date: Sun, 21 Nov 2004 19:56:41 +0100 [thread overview]
Message-ID: <41A0E4E9.3040902@colorfullife.com> (raw)
Hi Peter,
>Just a question: can kfree sleep?
>
>
>
>
No, it never sleeps. It's safe to call kfree from arbitrary context. The
only exception is the NMI oopser and similar arch code.
>I believe so, but slab.c does not enlighten me immediately:
>
>
Yes, the kfree code is quite long - it must check if freeing one object
created a freeable page and return it to the page allocator. Together
with lots of caching and debug checks.
--
Manfred
next reply other threads:[~2004-11-21 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 18:56 Manfred Spraul [this message]
2004-11-21 20:51 ` can kfree sleep? Peter T. Breuer
-- strict thread matches above, loose matches on Subject: below --
2004-11-21 12:23 Peter T. Breuer
2004-11-21 21:10 ` Andrew Morton
2004-11-21 21:14 ` Christoph Hellwig
2004-11-21 22:30 ` Peter T. Breuer
2004-11-22 5:41 ` Christoph Hellwig
2004-11-22 8:18 ` 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=41A0E4E9.3040902@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
/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