Messages in this thread | | | Subject | Re: Major slab mem leak with 2.6.17 / GCC 4.1.1 | From | Mike Galbraith <> | Date | Mon, 16 Oct 2006 09:08:30 +0000 |
| |
On Mon, 2006-10-16 at 09:07 +0100, Catalin Marinas wrote: > On 16/10/06, Mike Galbraith <efault@gmx.de> wrote: > > On Sun, 2006-10-15 at 07:59 +0000, Mike Galbraith wrote: > > > > > 2.6.19-rc1 + patch-2.6.19-rc1-kmemleak-0.11 compiles fine now (unless > > > CONFIG_DEBUG_KEEP_INIT is set), boots and runs too.. but axle grease > > > runs a lot faster ;-) I'll try a stripped down config sometime. > > > > My roughly three orders of magnitude (amusing to watch:) boot slowdown > > turned out to be stack unwinding. With CONFIG_UNWIND_INFO disabled, > > 2.6.19-rc2 + patch-2.6.19-rc1-kmemleak-0.11 runs just fine. > > Kmemleak introduces some overhead but shouldn't be that bad. > DEBUG_SLAB also introduces an overhead by erasing the data in the > allocated blocks.
2.6.18 with your rc6 patch booted normally with stack unwind enabled.
-Mike
- 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/
| |