* kmalloc question
@ 2003-10-09 1:06 Finney, Steve
2003-10-09 1:06 ` Finney, Steve
2003-10-09 8:09 ` Ralf Baechle
0 siblings, 2 replies; 5+ messages in thread
From: Finney, Steve @ 2003-10-09 1:06 UTC (permalink / raw)
To: linux-mips
Is kmalloc (GFP_KERNEL) on a 32 bit HIGHMEM enabled MIPS kernel (BCM/Sibyte processor) guaranteed to allocate memory from the low, KSEG0/1 addressible region? I'm having trouble sorting through the slab.c code. On this processor, only 256 MB of DRAM is directly addressible; with more than 256 MB of RAM, there is 256 MB in zone 0, and the remainder in zone 2. Zone 1 is empty.
Thanks,
sf
^ permalink raw reply [flat|nested] 5+ messages in thread
* kmalloc question
2003-10-09 1:06 kmalloc question Finney, Steve
@ 2003-10-09 1:06 ` Finney, Steve
2003-10-09 8:09 ` Ralf Baechle
1 sibling, 0 replies; 5+ messages in thread
From: Finney, Steve @ 2003-10-09 1:06 UTC (permalink / raw)
To: linux-mips
Is kmalloc (GFP_KERNEL) on a 32 bit HIGHMEM enabled MIPS kernel (BCM/Sibyte processor) guaranteed to allocate memory from the low, KSEG0/1 addressible region? I'm having trouble sorting through the slab.c code. On this processor, only 256 MB of DRAM is directly addressible; with more than 256 MB of RAM, there is 256 MB in zone 0, and the remainder in zone 2. Zone 1 is empty.
Thanks,
sf
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmalloc question
2003-10-09 1:06 kmalloc question Finney, Steve
2003-10-09 1:06 ` Finney, Steve
@ 2003-10-09 8:09 ` Ralf Baechle
1 sibling, 0 replies; 5+ messages in thread
From: Ralf Baechle @ 2003-10-09 8:09 UTC (permalink / raw)
To: Finney, Steve; +Cc: linux-mips
On Wed, Oct 08, 2003 at 03:06:50PM -1000, Finney, Steve wrote:
> Is kmalloc (GFP_KERNEL) on a 32 bit HIGHMEM enabled MIPS kernel (BCM/Sibyte processor) guaranteed to allocate memory from the low, KSEG0/1 addressible region? I'm having trouble sorting through the slab.c code. On this processor, only 256 MB of DRAM is directly addressible; with more than 256 MB of RAM, there is 256 MB in zone 0, and the remainder in zone 2. Zone 1 is empty.
Yes.
Ralf
^ permalink raw reply [flat|nested] 5+ messages in thread
* kmalloc question
@ 2002-06-05 5:25 Andre.Messerschmidt
2002-06-05 17:24 ` Alan Cox
0 siblings, 1 reply; 5+ messages in thread
From: Andre.Messerschmidt @ 2002-06-05 5:25 UTC (permalink / raw)
To: linux-mips
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?
regards
--
Andre Messerschmidt
Application Engineer
Infineon Technologies AG
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmalloc question
2002-06-05 5:25 Andre.Messerschmidt
@ 2002-06-05 17:24 ` Alan Cox
0 siblings, 0 replies; 5+ messages in thread
From: Alan Cox @ 2002-06-05 17:24 UTC (permalink / raw)
To: Andre.Messerschmidt; +Cc: linux-mips
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-10-09 8:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-10-09 1:06 kmalloc question Finney, Steve
2003-10-09 1:06 ` Finney, Steve
2003-10-09 8:09 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 5:25 Andre.Messerschmidt
2002-06-05 17:24 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox