3 ms·
Deep recursion is a bad idea in the kernel too; that doesn't mean it's a bad idea. Code running in the kernel has a limited stack space. I think it's tiny, som
by kazinator 5y ago
Deep recursion is a bad idea in the kernel too; that doesn't mean it's a bad idea.
Code running in the kernel has a limited stack space. I think it's tiny, something like just a few pages.
Interrupts (which can nest) run in that stack space, not just the mainline code in syscall context. I think that might have changed though (there are interrupt specific stacks), which might also depend on the specific arch port of Linux. Still, those stacks are small and all the caveats apply to interrupt context. Don't be searching a linked list with linear recursion or using crazy VLA's.
If I had to put virtual machine execution into the kernel, though, I would definitely use VLA's or alloca to get the space required for each function to be as tight as possible to its actual requirements, the same way that the C compiler emits code for each function to allocate its frame size to exactly the needed size. Right tool for the right job.