public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Stemen <linuxkernel@AdvancedResearch.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linuxkernel@AdvancedResearch.org (Vincent Stemen)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Plain 2.4.5 VM... (and 2.4.5-ac3)
Date: Tue, 29 May 2001 16:36:37 -0500	[thread overview]
Message-ID: <01052916363700.00493@quark> (raw)
In-Reply-To: <E154pvH-0004q1-00@the-village.bc.nu>
In-Reply-To: <E154pvH-0004q1-00@the-village.bc.nu>

On Tuesday 29 May 2001 15:16, Alan Cox wrote:
> > a reasonably stable release until 2.2.12.  I do not understand why
> > code with such serious reproducible problems is being introduced into
> > the even numbered kernels.  What happened to the plan to use only the
>
> Who said it was introduced ?? It was more 'lurking' than introduced. And
> unfortunately nobody really pinned it down in 2.4test.
>

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

  reply	other threads:[~2001-05-29 21:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  2:32 Plain 2.4.5 VM G. Hugh Song
2001-05-29  4:10 ` Jakob Østergaard
2001-05-29  4:26   ` safemode
2001-05-29  4:38     ` Jeff Garzik
2001-05-29  6:04       ` Mike Galbraith
2001-05-29 14:06       ` Gerhard Mack
2001-05-29  4:46   ` G. Hugh Song
2001-05-29  4:57     ` Jakob Østergaard
2001-05-29  7:13   ` Marcelo Tosatti
2001-05-29  9:10   ` Alan Cox
2001-05-29 15:37     ` elko
2001-05-29 20:09       ` Plain 2.4.5 VM... (and 2.4.5-ac3) Vincent Stemen
2001-05-29 20:16         ` Alan Cox
2001-05-29 21:36           ` Vincent Stemen [this message]
2001-05-30  6:02             ` Mike Galbraith
2001-05-30 19:58               ` Vincent Stemen
2001-05-30 20:11                 ` Alan Cox
2001-05-30 20:17                 ` Mike Galbraith
2001-05-31  3:47                   ` Vincent Stemen
2001-05-31  6:18                     ` Mike Galbraith
2001-05-30 20:30                 ` Rik van Riel
2001-05-31  3:11                   ` Vincent Stemen
     [not found]                 ` <991254700.786.0.camel@tux.bitfreak.net>
2001-05-30 21:59                   ` Vincent Stemen
2001-05-30 20:16             ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2001-05-31 17:23 Benjamin Redelings I

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01052916363700.00493@quark \
    --to=linuxkernel@advancedresearch.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox