From: Roger Luethi <rl@hellgate.ch>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm@kvack.org
Subject: Re: VM benchmarks
Date: Mon, 2 Feb 2004 17:50:44 +0100 [thread overview]
Message-ID: <20040202165044.GA8156@k3.hellgate.ch> (raw)
In-Reply-To: <401D95C2.3080208@cyberone.com.au>
On Mon, 02 Feb 2004 11:11:46 +1100, Nick Piggin wrote:
> efax is a compilation as well. I would be up for trying it, but it
The main advantage of efax over kbuild is that it is completely immune
to unfairness. And it used to have a low variance (in 2.4). Other than
that, access patterns are similar enough to make me suspect that gcc
loads are all quite similar.
> needs quite a lot of GUI dev libraries installed to compile it.
>
> I'll get onto it sometime I suppose, but for now I'll try to leave
> my test box unchanged.
You can actually do something like which shouldn't require the
dependencies on the test box:
/usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.3/cc1plus -fpreprocessed efaxi586.ii \
-quiet -O2 -Wall -fexceptions -frtti -fsigned-char -fno-check-new -o main.s
All you need is the preprocessed code.
I can test a couple of patches I you care, though. Which ones?
Roger
--
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-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-02-02 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 23:36 Nick Piggin
2004-02-02 0:08 ` Andrew Morton
2004-02-02 0:11 ` Nick Piggin
2004-02-02 6:31 ` Martin J. Bligh
2004-02-02 7:51 ` Nick Piggin
2004-02-02 16:50 ` Roger Luethi [this message]
2004-02-02 23:17 ` Nick Piggin
2004-02-03 23:16 ` Roger Luethi
2004-02-04 0:13 ` Nick Piggin
2004-02-04 15:27 ` Koni
2004-02-04 15:57 ` Martin J. Bligh
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=20040202165044.GA8156@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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