So... I know that there is some small-ish amount of kernel stack space
available per-process, and the kernel uses this area when executing on a
process's behalf (system call, etc). Let's say I allocate (via an
automatic/stack-based storage) some smallish structure which I want a
kernel thread to populate (or interrupt context... some context other than
my process's context).
If my process gets context swapped, is my kernel-based stack pointer
always valid?
Why use stack-based storage, you ask? Let's pretend this is a
high-frequency call and I don't want to incur the expense of kmalloc'ing
and freeing on every call. I know I have enough stack space, I just don't
know if my stack is always available :)
TIA!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
