> vfree() isn't allowed? I know vmalloc() isn't because it might sleep
> while waiting for the VM getting a few free pages. Why vfree isn't
> allowed? I can't see why freeing ressources is a problem ...
vfree() needs the semaphore vmalloc also uses. It's a semaphore because
vmalloc sleeps....
vmalloc/vfree are intended for slow-path only so it ought to not be a
problem....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/