Re: Major slab mem leak with 2.6.17 / GCC 4.1.1

On 16/10/06, Mike Galbraith <[email protected]> wrote:

On Mon, 2006-10-16 at 09:07 +0100, Catalin Marinas wrote:
> 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.

The only difference is that kmemleak now uses save_stack_trace() to
generate the call chain. In the previous versions I implemented a
simple stack backtrace myself, with the disadvantage that it only
worked on ARM and x86.

I think kmemleak should use the common stack trace API and investigate
why it is slower (either save_stack_trace is slower with stack unwind
enabled or kmemleak doesn't use these functions properly).

--
Catalin
-
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/

---

• Follow-Ups:
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: Mike Galbraith <[email protected]>

• References:
  • Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: [email protected]
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: "Pekka Enberg" <[email protected]>
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: "Catalin Marinas" <[email protected]>
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: Mike Galbraith <[email protected]>
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: Mike Galbraith <[email protected]>
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: "Catalin Marinas" <[email protected]>
  • Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
    • From: Mike Galbraith <[email protected]>

• Prev by Date: [Patch 2/3] Driver core: Change function call order in device_bind_driver().
• Next by Date: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.
• Previous by thread: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
• Next by thread: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
• Index(es):
  • Date
  • Thread

[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]