mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: arjan@fenrus.demon.nl
To: jalvo@mbay.net (John Alvord)
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel changes
Date: Sat, 29 Sep 2001 18:23:15 +0100	[thread overview]
Message-ID: <E15nNpb-0002KX-00@fenrus.demon.nl> (raw)
In-Reply-To: <Pine.LNX.4.20.0109290937510.18362-100000@otter.mbay.net>

In article <Pine.LNX.4.20.0109290937510.18362-100000@otter.mbay.net> you wrote:

> One aspect that bothers me is the absence of a success criteria.

I disagree here. Red Hat uses "must pass the cerberus test" as one of the
criteria for kernels. The are other similar criteria, most are obvious (must
boot :). All other distributions have similar tests and a few even use the
cerberus testsuite as well.

Maybe your problem is "absence of tests before Linus releases", well 
even that isn't fully true as distros run these tests on -pre kernels as
well (or -ac kernels, which are mostly in sync with -pre kernels)...

> The current competition for best VM is a good example. The fact is that
> every operating system will fail with a high enough load. The best you can
> hope for is a better degradation then the prior release.

There are a few basic creteria here as well, and 2.4.10 fails on some of
them so far:

1) Must not kill processes as long as there is plenty of swap
   or (possibly dirty) cache memory
2) Must not deadlock (as that is a code-bug)
3) Must not livelock without any progress

Note that no 2.4 kernel so far really achieves 1) in the presence of
highmem; the obvious deadlocks are just pushed further by tuning.

> At the moment both 2.4.10 and 2.4.9-ac16 are better then 2.2.19. But
> people keep testing under higher and higher loads and (surprise) they both
> fail... initiating a search for better degradation logic.

2.4.10 isn't better than 2.2.19 given the criteria above. 2.4.10aa2 might
be though... and 2.4.9acX+Rik's patches are solid in testing. 

Greetings,
   Arjan van de Ven




  reply	other threads:[~2001-09-29 17:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 21:32 Pavel Zaitsev
2001-09-28 22:04 ` Mark Frazer
2001-09-28 22:31   ` Ben Greear
2001-09-28 22:33   ` Alan Cox
2001-10-01  9:07     ` Paul Larson
2001-09-28 22:06 ` Alan Cox
2001-09-29 13:43   ` Andrew Ebling
2001-09-29  7:25 ` Mika Liljeberg
2001-09-29 10:19 ` Ville Herva
2001-09-29 16:45   ` John Alvord
2001-09-29 17:23     ` arjan [this message]
2001-09-30  8:17       ` John Alvord
2001-10-01 17:07     ` Martin J. Bligh
     [not found] <fa.b97kd6v.8j2vhi@ifi.uio.no>
     [not found] ` <fa.hmvo4bv.l2gsaj@ifi.uio.no>
2001-09-29  7:29   ` Dan Maas
2001-10-04  0:36     ` bill davidsen
2001-10-04  9:43       ` John Alvord

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=E15nNpb-0002KX-00@fenrus.demon.nl \
    --to=arjan@fenrus.demon.nl \
    --cc=jalvo@mbay.net \
    --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®