linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] fix for VM  test9-pre7
Date: Mon, 02 Oct 2000 17:20:25 -0400	[thread overview]
Message-ID: <39D8FC19.CD089EB6@mountain.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0010021250180.22539-100000@duckman.distro.conectiva>

[Linus removed from CC]
Rik van Riel wrote:
> 
> On Mon, 2 Oct 2000, Tom Leete wrote:
> 
> > I ran lmbench on test9-pre7 with and without the patch.
> >
> > Test machine was a slow medium memory UP box:
> > Cx586@120Mhz, no optimizations, 56M
> >
> > I still experience instability on this machine with both the
> > patched and vanilla kernel. It usually takes the form of
> > sudden total lockups, but on occasion I have seen oops +
> > panic at boot.
> 
> If you could decode the oops or mail us the panic, we
> might find out if this is a VM related problem or not...

I posted one to l-k recently. Time pressure prevented me
getting these.
No guarantee they are the same.

The lockups are clearly from irq handlers. They seem
associated with ide and net.

> 
> > This summary doesn't show any performance advantage to the
> > patch, but the detailed plots show that memory access
> > latency degrades more gracefully wrt array size.
> 
> That's because this benchmark has a very artificial page
> access pattern, that doesn't really benefit from any kind
> of page replacement. ;)
> 

The memory access latency issue showed up clearly. Without
the patch it is a step function at 16k array size. It looks
like vanilla always page faults for allocations bigger than
that. Your patch knocks the corner off that.

It's supposed to be easy to add tests to lmbench, but I've
never done it.

Cheers,
Tom
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-10-02 21:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-02  3:42 Rik van Riel
2000-10-02  8:18 ` Roger Larsson
2000-10-02 10:00   ` Ignore my: " Roger Larsson
2000-10-02 15:48     ` Rik van Riel
2000-10-02 15:45   ` Rik van Riel
2000-10-02 12:05 ` ehrhardt
2000-10-02 15:49   ` Rik van Riel
2000-10-02 12:27 ` Tom Leete
2000-10-02 15:51   ` Rik van Riel
2000-10-02 21:20     ` Tom Leete [this message]
2000-10-02 16:46 ` Christoph Rohland
2000-10-02 17:17   ` Rik van Riel
2000-10-04  7:45     ` Christoph Rohland

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=39D8FC19.CD089EB6@mountain.net \
    --to=tleete@mountain.net \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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