Re: kernel stack torture
Eric Youngdale (eric@aib.com)
Wed, 21 Feb 1996 15:09:45 -0500
>> Actually there still is a slight dependency here - until we scan the
>>bus, we don't know how much DMA memory to allocate for the pool, so when
we
>>start scanning the bus, the pool is empty. Thus we grab something off the
>>stack to use temporarily.
>
>Are you referring to the scsi_malloc() pool, or what happens when you do a
>kmalloc() with a GFP_DMA flag? If it's the former, I don't see why we
can't
>use a kmalloc() when scanning the SCSI bus (although in the usual case, we
At boot time, you probably could. When loading modules, the
memory might be rather tight, and as a result, kmalloc might not return
immediately. Still, I cannot see how this would be harmful for this
one special case.
-Eric
--
"The woods are lovely, dark and deep. But I have promises to keep,
And lines to code before I sleep, And lines to code before I sleep."