Re: CONFIG_KALLSYMS_EXTRA_PASS

Quoting Steven Rostedt <rostedt@xxxxxxxxxxx>:

> On Wed, 2005-05-18 at 00:27 +0100, pmarques@xxxxxxxxxxxx wrote:
> 
> > You can try the very crude (but effective) way to check if this is your
> problem
> > or not. Go to scripts/kallsyms.c and change:
> > 
> > #define WORKING_SET             1024
> > 
> > to:
> > 
> > #define WORKING_SET             65536
> > 
> 
> Yep, that did the trick. Thanks.  And just to make sure, I put it back
> to 1024, recompiled, and got the error again.
> 
> > This will force kallsyms to use *all* the symbols for the compression, and
> the
> > size of the result won't be affected by the symbol positions.
> > 
> > [...]
> 
> Your patch sounds too good to not be included even if this wasn't the
> case. How come it hasn't been applied before?

This is not really the patch, its just a quick fix. The problem with this fix is
that, not only it will take a lot more memory to build the kallsyms data, it
will take about 6 seconds on a P4 2.8GHz to compress 20000 symbols which is
about the number of symbols of a i386 defconfig, IIRC.

The actual patch must still use a small working set of symbols to improve
performance, but keep the token data from the first pass to use on the second.
This will actually decrease the time for the kallsyms calculation instead of
increasing it, as the previous solution did.

I've still not written the patch because I was waiting for some confirmation
that it would have some chance of acceptance. I guess I'll just write it and
send it upstream and see how that goes.

Thanks for taking the time to confirm the problem,

--
Paulo Marques
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/