Prev: [BSG]: Add support for struct sg_io_v4->d[out,in]_iovec_count
Next: [BSG]: Add support for struct sg_io_v4->d[out,in]_iovec_count
From: Jeffrey Merkey on 14 Jun 2010 02:40
I have been running down bugs on the MDB Debugger on a 4 processor AMD
Opteron System and have discovered that processors 1-X (other than 0)
use a buttload of stack space when all the spinlock debgguging checks
are turned on -- way too much memory and the systenter_past_esp panic
shows up a lot. NetWare at one point instrumented the ability to page
map an extra 4K of memory up to 16K (then release it when the stack
shrunk back to a smaller usage footprint). I think for debugging and
just general usage you should enable a 16K pagable limit with 4K
stacks for debuggers and such or just to stop a lot of dump traps.

It's getting to the point where 8K wont be enough when people need to
debug spinlocks and rcu locks and other types of breakage. Would not
be hard to instrument.

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [BSG]: Add support for struct sg_io_v4->d[out,in]_iovec_count
Next: [BSG]: Add support for struct sg_io_v4->d[out,in]_iovec_count