more debugging enabled in rawhide kernels.

[Clemens Eisserer]

It has a horrible impact at least on Intel's driver performance.
I've run some benchmarks, which show half the performance.

This could be due to the update to 2.8.0 or due to debugging enabled.

- Clemens

2009/6/25 Dave Jones <davej at redhat.com>:
> On Thu, Jun 25, 2009 at 04:53:27PM +0100, Richard W.M. Jones wrote:
>  > On Wed, Jun 24, 2009 at 08:08:40PM -0400, Dave Jones wrote:
>  > > In tomorrows rawhide kernel, I've enabled a debugging option
>  > > called kmemleak. As the name suggests, this tracks memory allocations,
>  > > and prints backtraces in cases where the memory is believed to be lost.
>  >
>  > As a general comment, I see many backtraces when I run the libguestfs
>  > testsuite.  Most are harmless, in that they don't appear to affect the
>  > running of programs, so I don't report them.  But is it helpful to
>  > report these?  If so how - open BZs for each variation that I see?
>
> Everything I've seen so far looks like a false positive.
> The next build should reduce the number of these (hopefully dramatically).
>
> So for now, just hold off on filing anything.
>
>        Dave
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>