Re: Anything special with kmem_map and mb_map?

:I have been wondering this for some time. There are many kernel :submaps: exec_map, clean_map, :etc. But if you look the code in vm_map_find(), we have to call splvm() :for kmem_map and its :submap mb_map, but not for other kernel submaps. So is there anything :special with these two :kernel s

Anything special with kmem_map and mb_map?

I have been wondering this for some time. There are many kernel submaps: exec_map, clean_map, etc. But if you look the code in vm_map_find(), we have to call splvm() for kmem_map and its submap mb_map, but not for other kernel submaps. So is there anything special with these two kernel submaps

Re: Anything special with kmem_map and mb_map?

:I have been wondering this for some time. There are many kernel :submaps: exec_map, clean_map, :etc. But if you look the code in vm_map_find(), we have to call splvm() :for kmem_map and its :submap mb_map, but not for other kernel submaps. So is there anything :special with these two :kernel

Anything special with kmem_map and mb_map?

I have been wondering this for some time. There are many kernel submaps: exec_map, clean_map, etc. But if you look the code in vm_map_find(), we have to call splvm() for kmem_map and its submap mb_map, but not for other kernel submaps. So is there anything special with these two kernel submap