From: Jens Axboe <axboe@suse.de>
To: Frank Cornelis <fcorneli@elis.rug.ac.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kmem_cache_alloc & kernel_lock
Date: Sun, 9 Dec 2001 16:47:21 +0100 [thread overview]
Message-ID: <20011209154721.GF28729@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0112091626110.27042-100000@trappist.elis.rug.ac.be>
In-Reply-To: <Pine.LNX.4.33.0112091626110.27042-100000@trappist.elis.rug.ac.be>
On Sun, Dec 09 2001, Frank Cornelis wrote:
> Hi,
>
> Can I use kmem_cache_alloc(mycache_cachep, SLAB_KERNEL) within
> a kernel_lock/kernel_unlock block? Or should it be SLAB_ATOMIC?
GFP_KERNEL is ok, you can sleep with the kernel lock held.
--
Jens Axboe
next prev parent reply other threads:[~2001-12-09 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 15:30 kmem_cache_alloc & kernel_lock Frank Cornelis
2001-12-09 15:47 ` Jens Axboe [this message]
2001-12-09 17:43 ` Ingo Molnar
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=20011209154721.GF28729@suse.de \
--to=axboe@suse.de \
--cc=fcorneli@elis.rug.ac.be \
--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