From: "Martin J. Bligh" <mbligh@aracnet.com>
To: The One True Dave Barry <dave@zork.net>, linux-mm@kvack.org
Cc: sneakums@zork.net
Subject: Re: [PATCH] 2.4.20-rmap15a
Date: Tue, 03 Dec 2002 12:08:09 -0800 [thread overview]
Message-ID: <30200000.1038946087@titus> (raw)
In-Reply-To: <20021203195854.GA6709@zork.net>
> This is correct, and believe it or not i'm even using
> 2.4.19 + rmap15a, no other patches. I don't have my hard
> numbers available, but the difference between builds was quite
> significant, something like:
>
> 2.4.19 vanilla:
> real 85m
>
> 2.4.19-rmap15a:
> real 102m
Assuming the extra time is eaten in Sys, not User, can you get a profile
of each, & post them?
M.
--
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/
next prev parent reply other threads:[~2002-12-03 20:08 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
2002-12-03 19:58 ` The One True Dave Barry
2002-12-03 20:08 ` Martin J. Bligh [this message]
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=30200000.1038946087@titus \
--to=mbligh@aracnet.com \
--cc=dave@zork.net \
--cc=linux-mm@kvack.org \
--cc=sneakums@zork.net \
/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