I fail to see the distinction. First of all, why was it ever released
as 2.4-test? That question should probably be directed at Linus. If
it is not fully tested, then it should be released it as an odd
number. If it already existed in the odd numbered development kernel
and was known, then it should have never been released as a production
kernel until it was resolved. Otherwise, it completely defeats the
purpose of having the even/odd numbering system.
I do not expect bugs to never slip through to production kernels, but
known bugs that are not trivial should not, and serious bugs like
these VM problems especially should not.
> > By the way, The 2.4.5-ac3 kernel still fills swap and runs out of
> > memory during my morning NFS incremental backup. I got this message
> > in the syslog.
>
> 2.4.5-ac doesn't do some of the write throttling. Thats one thing I'm
> still working out. Linus 2.4.5 does write throttling but Im not convinced
> its done the right way
>
> > completely full. By that time the memory was in a reasonable state
> > but the swap space is still never being released.
>
> It wont be, its copied of memory already in apps. Linus said 2.4.0 would
> need more swap than ram when he put out 2.4.0.
>
I do not like that at all. I should not have to have to tie up a
bunch of extra hard drive space for swap if I have plenty of RAM for
90% of my usage. During the 2.0.x days I was always able to run with
a small swap or no swap at all when I had 80-128Mb RAM and it was
always rock solid. It seems to me that the swap space should just add
to your virtual memory and the size ratio between swap and RAM should
not matter.
- Vincent Stemen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/