YAMAMOTO Takashi wrote:
>>> even if you never sleep, our kernel_map is not interrupt safe.
>>>   
>>>       
>> Yes, but the KM_NOSLEEP flag could be a hint to use an interrupt safe map.
>>     
>
> i don't think it's a good idea because it implies to make kmem_free complicate.
> ie. it has to figure out which map the region should be freed back to.
>
> YAMAMOTO Takashi
>   

Good point; I didn't consider that. I should probably look more closely
at our implementation. Or just STFU, I guess. Given current time
constraints, I'll probably do the latter. :-)

-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191