From: 520047054719-0001@t-online.de (Oliver Neukum)
To: Robert Love <rml@tech9.net>
Cc: arjan@fenrus.demon.nl, linux-kernel@vger.kernel.org
Subject: Re: current->state after kmalloc
Date: Tue, 5 Feb 2002 02:08:07 +0100 [thread overview]
Message-ID: <16Xu62-2F1K08C@fwd04.sul.t-online.com> (raw)
In-Reply-To: <m16XtOG-000OVeC@amadeus.home.nl> <16Xthq-147i9wC@fwd04.sul.t-online.com> <1012870211.1062.43.camel@phantasy>
In-Reply-To: <1012870211.1062.43.camel@phantasy>
On Tuesday 05 February 2002 01:50, Robert Love wrote:
> On Mon, 2002-02-04 at 19:43, Oliver Neukum wrote:
> > Is it safe with GFP_ATOMIC ?
>
> You are guaranteed kmalloc will not sleep if you use GFP_ATOMIC, yes.
>
> But I still find it gross to mark yourself sleeping but not sleep
> immediately.
usb_submit_urb() uses kmalloc internally.
To code a simple waiting for the results of an urb,
it is necessary.
Regards
Oliver
next prev parent reply other threads:[~2002-02-05 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 0:06 Oliver Neukum
2002-02-05 0:23 ` arjan
2002-02-05 0:43 ` Oliver Neukum
2002-02-05 0:50 ` Robert Love
2002-02-05 1:08 ` Oliver Neukum [this message]
2002-02-05 8:16 ` arjan
2002-02-05 8:35 ` Oliver Neukum
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=16Xu62-2F1K08C@fwd04.sul.t-online.com \
--to=520047054719-0001@t-online.de \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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®