linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
To: linux-mm@kvack.org
Cc: dave@zork.net
Subject: Re: [PATCH] 2.4.20-rmap15a
Date: Tue, 03 Dec 2002 16:39:06 +0000	[thread overview]
Message-ID: <6usmxfys45.fsf@zork.zork.net> (raw)
In-Reply-To: <Pine.LNX.4.44L.0212011833310.15981-100000@imladris.surriel.com> (Rik van Riel's message of "Sun, 1 Dec 2002 18:35:50 -0200 (BRST)")

commence  Rik van Riel quotation:

> This is a merge of rmap15a with marcelo's 2.4 bitkeeper tree,
> which is identical to 2.4.20-rc4 (he didn't push the makefile
> update).  The only thing left out of the merge for now is
> Andrew Morton's read_latency patch, both because I'm not sure
> how needed it is with the elevator updates and because this
> part of the merge was too tricky to do at merge time; I'll port
> over Andrew Morton's read_latency patch later...

I'm seeing a difference in wall-clock time of about nine minutes for
an lnx-bbc build (http://www.lnx-bbc.org/).  Dave Barry, another
lnx-bbc developer, has observed something similar.  The difference in
system times seems to be above noise, too.  Both of the kernels I used
also had Stephen Tweedie's ext3 updates for 2.4.20 applied[0].  I can
retest without, if you wish.  I believe Dave's kernels had only rmap
applied, however.

2.4.20:
real    106m26.147s
user    62m54.340s
sys     26m54.670s

2.4.20-rmap15a:
real    115m5.283s
user    63m50.580s
sys     29m34.520s

I used ccache with these builds and they are almost entirely cached
(the big exception being gcc), so the job becomes fairly I/O-bound as
a result.  The builds are quite big: the CVS tree unpacks and builds
about three hundred megabytes of source, resulting in a build
footprint of approximately 2.9GiB.  The volume I used for the build is
formatted as ext3, with htree activated.  (I originally started using
those patches because I had found that previous htree patches b0rked
during an lnx-bbc build.)


[0]  http://people.redhat.com/sct/patches/ext3-2.4/dev-20021115/

-- 
 /                          |
[|] Sean Neakums            |  Questions are a burden to others;
[|] <sneakums@zork.net>     |      answers a prison for oneself.
 \                          |
--
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/

  reply	other threads:[~2002-12-03 16:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01 20:35 Rik van Riel
2002-12-03 16:39 ` Sean Neakums [this message]
2002-12-03 19:58   ` The One True Dave Barry
2002-12-03 20:08     ` Martin J. Bligh
2002-12-03 20:56       ` Rik van Riel
2002-12-04 11:28         ` Sean Neakums
2002-12-04 13:33           ` Sean Neakums
2002-12-04 11:40         ` Arjan van de Ven
2002-12-04 12:12           ` Rik van Riel

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=6usmxfys45.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --cc=dave@zork.net \
    --cc=linux-mm@kvack.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