Scheduling feature freeze (was Re: [PATCH] mke2fs size reduction)
Rob Landley
rob at landley.net
Fri Sep 23 12:48:02 UTC 2005
On Friday 23 September 2005 04:09, Erik Andersen wrote:
> > What platforms is using a lot of stack space on bad? (And how much is
> > bad?) Busybox has developed a number of dependencies on the Linux kernel,
> > and I don't know of any Linux systems where the stack doesn't grow
> > dynamically. (What, mmu-less variants?)
>
> uClinux (mmu-less) has a fixed sized stack.
Yeah, that's mainstream for us.
Hmmm...
I really don't want to introduce another major overhaul of the code at this
point, because I'd like to get 1.1 out. (It's coming up on a year since 1.0
shipped, and yes we have 1.01 and I should probably start on 1.0.2 soon, but
right now we have numerous completed features languishing in the -devel
tree.)
Can we target the allocation overhaul for 1.2 (and bump the SuSv3 audit for
that, I'm afriad), and try to focus on beating 1.1 into shape for a release
with a feature freeze starting, say, the end of October?
That gives us another month and change for anything pending, and then we start
seriously fixing and testing. (He says, blithely knowing that one of his
current projects is a test suite revamp...)
Opinions?
Rob
More information about the busybox
mailing list