mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Aviv Shavit <avivshavit@yahoo.com>,
	Ken Brownfield <brownfld@irridia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: vm-33, strongly recommended [Re: [2.4.17/18pre] VM and swap - it's really unusable]
Date: Wed, 10 Apr 2002 16:40:22 -0600	[thread overview]
Message-ID: <200204102240.g3AMeMn16102@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20020410023006.B6875@dualathlon.random>

Andrea Arcangeli writes:
> On Tue, Apr 09, 2002 at 06:07:50PM -0600, Richard Gooch wrote:
> > Andrea Arcangeli writes:
> > > I recommend everybody to never use a 2.4 kernel without first applying
> > > this vm patch:
> > [...]
> > 
> > The way you write this makes it sound that the unpatched kernel is
> > very dangerous. Is this actually true? Or do you really just mean "the
> > patched kernel has better handling under extreme loads"?
> 
> The unpatched kernel isn't dangerous in the sense it won't destroy
> data, it won't corrupt memory and finally it won't deadlock on smp
> locks, but it can theoretically deadlock with oom and it has various
> other runtime issues starting from highmem balancing, too much
> swapping, lru list balancing, related-bhs in highmem, numa broken
> with += min etc... so IMHO it is better to _always_ use the patched
> kernel that takes care of all problems that I know of at the moment,
> plus it has further optimizations. OTOH for lots of workloads
> mainline is just fine, the deadlocks never trigger and the runtime
> behaviour is ok, but unless you are certain you don't need the
> vm-33.gz patch, I recommend to apply it.

So, in other words, 99.99% of users don't need to apply the patch.
They should, in order to have a better system, but 99.99% of them
won't notice the difference. That seems to be a more honest
recommendation than the "panic stations" alert that you posted.

Just because you want people to apply your patches, doesn't mean you
should resort to alarmist-sounding messages. Let's at least have truth
in advertising in one small corner of the world :-)

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2002-04-10 22:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 11:51 [2.4.17/18pre] VM and swap - it's really unusable Aviv Shavit
2002-02-26  0:09 ` Ken Brownfield
2002-02-26  4:40   ` Ken Brownfield
2002-04-09 20:45     ` Aviv Shavit
2002-04-09 21:16       ` Rik van Riel
2002-04-09 23:36       ` vm-33, strongly recommended [Re: [2.4.17/18pre] VM and swap - it's really unusable] Andrea Arcangeli
2002-04-10  0:07         ` Richard Gooch
2002-04-10  0:30           ` Andrea Arcangeli
2002-04-10 22:40             ` Richard Gooch [this message]
2002-04-10 23:51               ` Andrea Arcangeli
2002-04-10  8:55         ` Christoph Hellwig
2002-04-11 23:34         ` Ken Brownfield
2002-04-11 23:50           ` Aviv Shavit
2002-04-12  0:20             ` Andrea Arcangeli
2002-04-10  1:17 shane

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=200204102240.g3AMeMn16102@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=andrea@suse.de \
    --cc=avivshavit@yahoo.com \
    --cc=brownfld@irridia.com \
    --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

all inboxes | Powered by JetHome®