| To: | Andre.Messerschmidt@infineon.com |
|---|---|
| Subject: | Re: kmalloc question |
| From: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
| Date: | 05 Jun 2002 18:24:02 +0100 |
| Cc: | linux-mips@oss.sgi.com |
| In-reply-to: | <86048F07C015D311864100902760F1DD01B5EA6B@DLFW003A> |
| References: | <86048F07C015D311864100902760F1DD01B5EA6B@DLFW003A> |
| Sender: | owner-linux-mips@oss.sgi.com |
On Wed, 2002-06-05 at 06:25, Andre.Messerschmidt@infineon.com wrote: > Hi. > > I always thought that it is save to use kmalloc in an interrupt handler as > long as you use GFP_ATOMIC. > Now someone told me that it is not allowed to use these functions in any way > in an interrupt. > > Can please someone clarify me here? GFP_ATOMIC is safe in an interrupt handler. You might get NULL back and that it is your problem, but the kmalloc is safe |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Fwd: Current state of MIPS16 support?], law |
|---|---|
| Next by Date: | Re: [Fwd: Current state of MIPS16 support?], Daniel Jacobowitz |
| Previous by Thread: | kmalloc question, Andre . Messerschmidt |
| Next by Thread: | Re: [Fwd: Current state of MIPS16 support?], Dominic Sweetman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |