Re: bloat and debugging code
Zack Weinberg (zack@bitmover.com)
Fri, 23 Jul 1999 21:18:05 -0700
> > Add 32-byte alignment padding for every string, the increased size of
> > struct wait_queue, and the code for the macros themselves, and you can
> > see where the bloat is coming from.
>
> And the point being? It's -CURRENT, ferchrissake. In pretty unstable
> state. Vanilla 2.3.11 has a race in bdflush giving spontaneous reboots.
> 2.3.12-pre1 *seems* to fix it, but something still lurks there. Easily
> removable bloat from debugging is not a problem, IMHO.
Did I say it was a problem? I'm actually pleased to find the only
reason 2.3 is bigger is debugging. (Makes me want to go hack up ld
though...)
What's going on with bdflush?
zw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/