From: Gerrit Huizenga <gh@us.ibm.com>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@zip.com.au>,
William Lee Irwin III <wli@holomorphy.com>,
Rik van Riel <riel@conectiva.com.br>,
Dave McCracken <dmccr@us.ibm.com>,
Paul Larson <plars@austin.ibm.com>
Subject: LTP memory tests (fwd)
Date: Thu, 11 Jul 2002 14:32:18 -0700 [thread overview]
Message-ID: <E17SlXu-0005kt-00@w-gerrit2> (raw)
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
The Linux Test project has some tests for VM. I'm not sure
that all of them are enabled by a default run. I'd recommend
installing the LTP (ltp.sourceforge.net) and running it as a
minimal regression suite if you haven't done so already. It
is generally pretty quick and you could probably set up a run
list to focus on VM changes that would run much more quickly.
If you have some specific modifications, e.g.:
From: Andrew Morton <akpm@zip.com.au>
The problem is the access pattern. It shouldn't be
random-uniform. But what should it be? random-gaussian?
So: map a large file, access it random-gaussian. malloc
some memory, access it random-gaussian. Apply eviction
pressure. Measure throughput. Optimise throughput.
Does this not capture what the VM is supposed to do?
...or enhancments to the current tests that would make them more
useful, yell.
Paul's team typically focuses on functional tests rather than
performance tests. However, it may be possible to make a set
of deterministic tests that may also be useful for doing some
first level performance comparisons if written correctly. E.g.
random distributions with a settable initial seed.
gerrit
[-- Attachment #2: forwarded message --]
[-- Type: message/rfc822, Size: 1 bytes --]
reply other threads:[~2002-07-11 21:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E17SlXu-0005kt-00@w-gerrit2 \
--to=gh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=dmccr@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=plars@austin.ibm.com \
--cc=riel@conectiva.com.br \
--cc=wli@holomorphy.com \
/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